You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2015/05/12 21:44:00 UTC
[jira] [Comment Edited] (CASSANDRA-9364) Add a warning when a high
setting for rpc_max_threads is specified for HSHA
[ https://issues.apache.org/jira/browse/CASSANDRA-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540571#comment-14540571 ]
Brandon Williams edited comment on CASSANDRA-9364 at 5/12/15 7:43 PM:
----------------------------------------------------------------------
I would except that can depend on a lot of factors, but at least this way they get a red flag and know something might be wrong. Committed.
was (Author: brandon.williams):
I would except that can depend on a lot of factors, but at least this way they get a red flag and know something might wrong. Committed.
> Add a warning when a high setting for rpc_max_threads is specified for HSHA
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-9364
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9364
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 2.0.15, 2.1.6
>
> Attachments: 9364.txt
>
>
> In CASSANDRA-7594 we allowed configuring this. The problem is this was ignored for HSHA previously, so some people go through this scenario:
> 1. start with sync and 4000 threads
> 2. switch to HSHA, pre-7594
> 3. upgrade to a version after 7594, without changing this setting
> 4. experience awful performance due to insane thread contention
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)