You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2016/03/02 16:16:18 UTC
[jira] [Resolved] (CASSANDRA-8186) Revisit defaults for max rpc
threads
[ https://issues.apache.org/jira/browse/CASSANDRA-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko resolved CASSANDRA-8186.
------------------------------------------
Resolution: Won't Fix
Closing as {{Won't Fix}} as it's easily workaroundable, and Thrift is on its way out.
> Revisit defaults for max rpc threads
> ------------------------------------
>
> Key: CASSANDRA-8186
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8186
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jeremy Hanna
>
> Currently the rpc max threads defaults to unlimited. The dangers of doing that in certain circumstances were discussed on CASSANDRA-8116 and a warning was added to the yaml.
> I've worked with two clusters in the last couple of weeks that has had the heap full of rpc threads for this reason. I'm wondering if we should set a more reasonable default so that people don't hurt themselves unnecessarily.
> Is there a reason to not default this to perhaps 2048, what's commented out in the yaml? We could have a yaml comment about it as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)