[FLUME-2964] race condition in SpillableMemoryChannel log print

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 1.7.0
• Component/s: Channel
• Assignee: Unassigned
• Reporter: liqiaoping
• Created: 03/Aug/16 07:46
• Updated: 03/Aug/16 20:56
• Resolved: 03/Aug/16 07:53

Description

use SpillableMemoryChannel with http blob handler, and send many request concurrently, As the jetty has a threadpool to handle incoming request, the commit to SpillableMemoryChannel will be concurrent.

the Following code :

@Override
protected void doCommit() throws InterruptedException {
if (putCalled) {
putCommit();
if (LOGGER.isDebugEnabled())

{ LOGGER.debug("Put Committed. Drain Order Queue state : " + drainOrder.dump()); }

in method - >drainOrder.dump() will iterate its internal queue, in the meantime, has changed by other thread, thus throw a concurrent modification exception. thus will result the channel processor try to rollback, but actually the transaction has commit succefully.

Issue Links

• duplicates: FLUME-2965 race condition in SpillableMemoryChannel log print