Uploaded image for project: 'Flume'
  1. Flume
  2. FLUME-597

Fix handling interruption of blocked WALSource

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.9.4
    • None
    • None

    Description

      The getUnackedSource call in NaiveFileWALManager blocks if there are no elements to process in queue. If interrupted and the logged and sent queues are empty, this should exit cleanly. If both logged and sent queues are empty we can definitely exit with without error.

      If the logged queue still contains data, and this is interrupted, it should definitely fail.

      It is debatable if we should exit cleanly if the logged queue is empty and the sent queue is not (sent but not acked). This patch exits cleanly only if the ack has been received as well.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jmhsieh Jonathan Hsieh
            jmhsieh Jonathan Hsieh
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment