[
https://issues.apache.org/jira/browse/CASSANDRA-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078458#comment-14078458
]
Pavel Yaskevich edited comment on CASSANDRA-7594 at 7/29/14 10:00 PM:
----------------------------------------------------------------------
I have brought back old thread pool executor service which uses min/max RPC
threads settings in the attached patch, plus include new version of the
disruptor server which supports setting invocationExecutor, please give it a
spin and let me know how it works out for you, Rick.
Edit: Patch is against latest cassandra-2.0 branch.
was (Author: xedin):
I have brought back old thread pool executor service which uses min/max RPC
threads settings in the attached patch, plus include new version of the
disruptor server which supports setting invocationExecutor, please give it a
spin and let me know how it works out for you, Rick.
> Disruptor Thrift server worker thread pool not adjustable
> ---------------------------------------------------------
>
> Key: CASSANDRA-7594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7594
> Project: Cassandra
> Issue Type: Bug
> Reporter: Rick Branson
> Assignee: Pavel Yaskevich
> Fix For: 2.0.10
>
> Attachments: CASSANDRA-7594.patch,
> disruptor-thrift-server-0.3.6-SNAPSHOT.jar
>
>
> For the THsHaDisruptorServer, there may not be enough threads to run blocking
> StorageProxy methods. The current number of worker threads is hardcoded at 2
> per selector, so 2 * numAvailableProcessors(), or 64 threads on a 16-core
> hyperthreaded machine. StorageProxy methods block these threads, so this puts
> an upper bound on the throughput if hsha is enabled. If operations take 10ms
> on average, the node can only handle a maximum of 6,400 operations per
> second. This is a regression from hsha on 1.2.x, where the thread pool was
> tunable using rpc_min_threads and rpc_max_threads.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
