[
https://issues.apache.org/jira/browse/CASSANDRA-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201923#comment-14201923
]
mck commented on CASSANDRA-7594:
--------------------------------
After an upgrade to 2.0.11 i can't start the servers.
I get
{noformat}
java.lang.OutOfMemoryError: Java heap space
at
com.thinkaurelius.thrift.TDisruptorServer$SelectorThread.<init>(TDisruptorServer.java:543)
at
com.thinkaurelius.thrift.TDisruptorServer.<init>(TDisruptorServer.java:228)
at
org.apache.cassandra.thrift.THsHaDisruptorServer.<init>(THsHaDisruptorServer.java:51)
at
org.apache.cassandra.thrift.THsHaDisruptorServer$Factory.buildTServer(THsHaDisruptorServer.java:105)
at
org.apache.cassandra.thrift.TServerCustomFactory.buildTServer(TServerCustomFactory.java:56)
at
org.apache.cassandra.thrift.ThriftServer$ThriftServerThread.<init>(ThriftServer.java:130)
at org.apache.cassandra.thrift.ThriftServer.start(ThriftServer.java:56)
at
org.apache.cassandra.service.CassandraDaemon.start(CassandraDaemon.java:449)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:509)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
{noformat}
If i edit cassandra.yaml so that rpc_max_threads to 256 then i am able to start
the servers again.
> 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.11
>
> Attachments: CASSANDRA-7594.patch,
> disruptor-thrift-server-0.3.6-SNAPSHOT.jar, jstack.txt,
> thrift-server-0.3.7-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.3.4#6332)
