Flume
  1. Flume
  2. FLUME-1428

File Channel should not consider a file as inactive until all takes are committed.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: v1.2.0
    • Fix Version/s: v1.3.0
    • Component/s: Channel
    • Labels:
      None

      Description

      FlumeEventQueue removes fileID from fileIDCounts before commits are completed. See FLUME-1417 for background. This series of events would be problematic:
      File ( i )
      n puts
      commit
      n takes (file i is no longer in flume event queue fileIDCounts)

      file roll -> current active file in directory (File i+1)
      background worker kicks in -> removes file i.
      Note that the commit for the n takes has not taken place.

      We do keep 2 files per directory, but if a commit/rollback does not come and 2 files are rolled, we might have some issues.

      1. FLUME-1428.patch
        4 kB
        Hari Shreedharan
      2. FLUME-1428-1.patch
        4 kB
        Hari Shreedharan

        Issue Links

          Activity

          Hari Shreedharan created issue -
          Hari Shreedharan made changes -
          Field Original Value New Value
          Link This issue relates to FLUME-1417 [ FLUME-1417 ]
          Hari Shreedharan made changes -
          Assignee Hari Shreedharan [ hshreedharan ]
          Hari Shreedharan made changes -
          Attachment FLUME-1428.patch [ 12542239 ]
          Hari Shreedharan made changes -
          Attachment FLUME-1428.patch [ 12542239 ]
          Hari Shreedharan made changes -
          Attachment FLUME-1428.patch [ 12542240 ]
          Hari Shreedharan made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Hari Shreedharan made changes -
          Attachment FLUME-1428-1.patch [ 12542321 ]
          Brock Noland made changes -
          Description FlumeEventQueue removes fileID from fileIDCounts before commits are completed. See FLUME-1417 for background. This series of events would be problematic:
          File ( i )
          n puts
          commit
          n takes (file i is no longer in flume event queue fileIDCounts)

          file roll -> current active file in directory (File i+1)
          background worker kicks in -> removes file i.
          Note that the commit for the n takes has not taken place.

          We do keep 2 files per directory, but if a commit/rollback does not come and 2 files are rolled, we might have some issues.
            
          Brock Noland made changes -
          Description    FlumeEventQueue removes fileID from fileIDCounts before commits are completed. See FLUME-1417 for background. This series of events would be problematic:
          File ( i )
          n puts
          commit
          n takes (file i is no longer in flume event queue fileIDCounts)

          file roll -> current active file in directory (File i+1)
          background worker kicks in -> removes file i.
          Note that the commit for the n takes has not taken place.

          We do keep 2 files per directory, but if a commit/rollback does not come and 2 files are rolled, we might have some issues.
          Brock Noland made changes -
          Status Patch Available [ 10002 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Hari Shreedharan
              Reporter:
              Hari Shreedharan
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development