[
https://issues.apache.org/jira/browse/CASSANDRA-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176336#comment-14176336
]
Mike Adamson commented on CASSANDRA-8116:
-----------------------------------------
It's pretty much guaranteed to OOM because the number of handlers per
SelectorThread is based on the the max pool size which for the default is
Integer.MAX_VALUE. This change happened as part of CASSANDRA-7594.
I suppose you could check and throw if the value is Integer.MAX_VALUE but you
aren't going to be able to check every value. It also happens when the node is
started so is pretty immediate which is why I suggested a doc change rather
than a code change.
> HSHA fails with default rpc_max_threads setting
> -----------------------------------------------
>
> Key: CASSANDRA-8116
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8116
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Mike Adamson
> Assignee: Mike Adamson
> Priority: Minor
> Fix For: 2.0.11, 2.1.1
>
> Attachments: 8116.txt
>
>
> The HSHA server fails with 'Out of heap space' error if the rpc_max_threads
> is left at its default setting (unlimited) in cassandra.yaml.
> I'm not proposing any code change for this but have submitted a patch for a
> comment change in cassandra.yaml to indicate that rpc_max_threads needs to be
> changed if you use HSHA.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
