having the write or read stage fill up, will cause as a secondary
effect deserialization to fill up
moral: when you start getting timeout exceptions, have your clients
sleep for 100ms or otherwise back off (or maybe you just need to add
capacity)
On Thu, Jun 3, 2010 at 10:16 AM, Daniel Kluesing
I've had a few nodes crash (Out of heap), and when I pull the heap dump, there
are hundreds of thousands of MessageDeserializationTasks in the thread pool
executor, using up GB of the heap. I'm running 0.6.2 on sun jvm u20 and the
nodes are under heavy load. Has anyone else run into this? I have
