[
https://issues.apache.org/jira/browse/CASSANDRA-8969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208605#comment-15208605
]
Sylvain Lebresne commented on CASSANDRA-8969:
---------------------------------------------
bq. you could potentially have 2x in-flight requests being kept in memory
Not totally sure I follow. Are we talking about the request objects? Because
those are really tiny and I don't that being that relevant. Besides, the number
of max in-flight queries is currently really limited by the number of native
transport threads, and I'm not sure to see in which way a bigger rpc timeouts
changes much here.
Anyway, feel free to check the attached patch to see if we're talking of the
same thing with different words. But if we aren't, I'm not sure to understand
the problem you're mentioning.
> 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)
