Affects Version/s: 0.92.0
Fix Version/s: 0.92.0
Yesterday debugging w/ Jack we noticed that with few handlers on a big box, he was seeing stats like this:
We had 2500 items in the rpc queue waiting to be processed.
Turns out he had too few handlers for number of clients (but also, it seems like he figured hw issues in that his RAM bus was running at 1/4 the rate that it should have been running at).
Chatting w/ J-D this morning, he asked if the queues hold 'data'. The queues hold 'Calls'. Calls are the client request. They contain data.
Jack had 2500 items queued. If each item to insert was 1MB, thats 25k * 1MB of memory that is outside of our generally accounting.
Currently the queue size is handlers * MAX_QUEUE_SIZE_PER_HANDLER where MAX_QUEUE_SIZE_PER_HANDLER is hardcoded to be 100.
If the queue is full we block (LinkedBlockingQueue).
Going to change the queue size from 100 to 10 by default – but also will make it configurable and will doc. this as possible cause of OOME. Will try it on production here before committing patch.
|Affects Version/s||0.92.0 [ 12314223 ]|
|Affects Version/s||0.90.3 [ 12316313 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||0.92.0 [ 12314223 ]|
|Resolution||Fixed [ 1 ]|
|Assignee||stack [ stack ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|284d 4h 42m||1||stack||31/Jan/12 21:42|