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

MemoryChannel should push events back into channel on rollback

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • NG alpha 1
    • NG alpha 1
    • None
    • None

    Description

      Currently the MemoryChannel (i.e. the "best effort" channel) transaction provider drops events if the consumer rolls back. In other words a sink that does:

      tx = channel.getTransaction()
      event = channel.take()
      tx.rollback()
      

      ...loses the event. Instead, the event should be pushed back into the channel so it's redelivered. Ideally, it should be inserted at the end of the channel to be as close to totally ordered as possible. There is the question of what to do if the channel is at capacity.

      Attachments

        1. Flume-772.patch
          14 kB
          Prasad Suresh Mujumdar
        There are no Sub-Tasks for this issue.

        Activity

          People

            prasadm Prasad Suresh Mujumdar
            esammer Eric Sammer
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: