[
https://issues.apache.org/jira/browse/CASSANDRA-8969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208691#comment-15208691
]
J.B. Langston commented on CASSANDRA-8969:
------------------------------------------
I agree this could be a good warning to have. I've seen a lot of customers
naively increase the timeout. Usually it's caused by I/O not keeping up with
requests, but a lot of users won't take the time to figure that out. They just
see their application timing out and they see something in cassandra.yaml
called timeout so they increase it without thinking of the cost. Now they have
GC death spiral and OOM to contend with in addition to the original problem.
> Add indication in cassandra.yaml that rpc timeouts going too high will cause
> memory build up
> --------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-8969
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8969
> Project: Cassandra
> Issue Type: Improvement
> Components: Configuration
> Reporter: Jeremy Hanna
> Assignee: Jeremy Hanna
> Priority: Minor
> Labels: lhf
> Fix For: 3.x
>
> Attachments: 8969.txt
>
>
> It would be helpful to communicate that setting the rpc timeouts too high may
> cause memory problems on the server as it can become overloaded and has to
> retain the in flight requests in memory. I'll get this done but just adding
> the ticket as a placeholder for memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
