On Mon, Apr 25, 2011 at 12:21 PM, Jonathan Ellis <jbel...@gmail.com> wrote: > I bet the problem is with the other tasks on the executor that Gossip > heartbeat runs on. > > I see at least two that could cause blocking: hint cleanup > post-delivery and flush-expired-memtables, both of which call > forceFlush which will block if the flush queue + threads are full. > > We've run into this before (CASSANDRA-2253); we should move Gossip > back to its own dedicated executor or it will keep happening whenever > someone accidentally puts something on the "shared" executor that can > block. > > Created https://issues.apache.org/jira/browse/CASSANDRA-2554 to fix > this. Thanks for tracking down the problem!
This is good to have too, but isn't the problem: I broke it in the gossiper refactoring. https://issues.apache.org/jira/browse/CASSANDRA-2565 -Brandon
