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

MemoryChannel should poll with timeout on take() rather than block indefinitely

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • NG alpha 1
    • NG alpha 1
    • None
    • None

    Description

      MemoryChannel is currently completely blocking; it uses ArrayBlockingQueue#put() and #take() rather than offer() and poll(). This is suboptimal for certain runner strategies and background tasks. For now, MemoryChannel should use #poll where x is some reasonable (ideally configurable) timeout.

      Attachments

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

          People

            esammer Eric Sammer
            esammer Eric Sammer
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment