incubator-flume-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Juhani Connolly" <>
Subject Re: Review Request: FLUME-936 MemoryChannel is not thread safe
Date Mon, 06 Feb 2012 01:37:09 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated 2012-02-06 01:37:09.579940)

Review request for Flume.


This is a final patch(unless someone runs into problems with it).
Updated for the latest 728 and I made the tests independent of each other to avoid problems
with mvn's parallel testing.
Everything runs through the full test suite in mvn without errors, and the new tests include
checking that no data is lost with multiple threads parallel put/taking.


This is an initial go at fixing the threading issues with memory channel. 

It uses the preliminary work on FLUME-935 and I have included the code from that.

The tagging of the events became unnecessary so I dropped that. One thing that concerns me
slightly is how to deal with not having enough space in the queue to rollback failed takes.
One method would be to keep a minimum buffer of transactionCapacity. Another would be to implement
the queue of queues as suggested in FLUME-889

Anyway, just putting up this early version to see what people think

This addresses bug FLUME-936.

Diffs (updated)

  flume-ng-core/src/main/java/org/apache/flume/channel/ PRE-CREATION

  flume-ng-core/src/main/java/org/apache/flume/channel/ PRE-CREATION

  flume-ng-core/src/main/java/org/apache/flume/channel/ PRE-CREATION 
  flume-ng-core/src/main/java/org/apache/flume/channel/ d379b64 
  flume-ng-core/src/test/java/org/apache/flume/channel/ b44030e 
  flume-ng-core/src/test/java/org/apache/flume/channel/ PRE-CREATION

  flume-ng-core/src/test/java/org/apache/flume/channel/ d18045b

  flume-ng-core/src/test/java/org/apache/flume/source/ 46e42e3 
  flume-ng-node/src/test/java/org/apache/flume/source/ 9e465e1 



The original tests pass, though I had to take out the state checks because of the changes
to semantics from the flume-935 code. I also had to add a transaction.close statement where
semantics were not properly being followed
I have to retrofit my new concurrency test since without the tagged events it cannot fail
without checking that the content is correct. I'll put that up asap, just wanted to get some
eyes on this before I head out.



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message