cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8116) HSHA fails with default rpc_max_threads setting
Date Fri, 24 Oct 2014 17:31:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183080#comment-14183080
] 

Tyler Hobbs commented on CASSANDRA-8116:
----------------------------------------

bq. is there any reason to have a default of unlimited? it just seems like it would be a simple
change to have a reasonable default.

I'm not sure about the rationale for that default.  Would you mind opening a new ticket to
discuss a better default?  I'm not sure if it's something we would want to change in 2.0 or
2.1.

> 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: Tyler Hobbs
>            Priority: Minor
>             Fix For: 2.0.12, 2.1.2
>
>         Attachments: 8116-throw-exc-2.0.txt, 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)

Mime
View raw message