[cassandra] branch cassandra-3.11 updated: Add indication in cassandra.yaml that rpc timeouts going too high will cause memory build up

[be...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

bereng pushed a commit to branch cassandra-3.11
in repository https://gitbox.apache.org/repos/asf/cassandra.git


The following commit(s) were added to refs/heads/cassandra-3.11 by this push:
     new 7c067b6  Add indication in cassandra.yaml that rpc timeouts going too high will cause memory build up
7c067b6 is described below

commit 7c067b6d7de84b988dc1cd465313d413674283fe
Author: Bereng <be...@gmail.com>
AuthorDate: Mon Sep 27 10:36:58 2021 +0200

    Add indication in cassandra.yaml that rpc timeouts going too high will cause memory build up
    
    patch by Berenguer Blasi, Jeremy Hanna; reviewed by Andres de la Peña for CASSANDRA-8969
    
    Co-authored-by: Berenguer Blasi <be...@gmail.com>
    Co-authored-by: Jeremy Hanna <je...@gmail.com>
---
 conf/cassandra.yaml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml
index 0626f4c..48bf0b4 100644
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@ -852,6 +852,19 @@ sstable_preemptive_open_interval_in_mb: 50
 # When unset, the default is 200 Mbps or 25 MB/s
 # inter_dc_stream_throughput_outbound_megabits_per_sec: 200
 
+# Server side timeouts for requests. The server will return a timeout exception
+# to the client if it can't complete an operation within the corresponding
+# timeout. Those settings are a protection against:
+#   1) having client wait on an operation that might never terminate due to some
+#      failures.
+#   2) operations that use too much CPU/read too much data (leading to memory build
+#      up) by putting a limit to how long an operation will execute.
+# For this reason, you should avoid putting these settings too high. In other words, 
+# if you are timing out requests because of underlying resource constraints then 
+# increasing the timeout will just cause more problems. Of course putting them too 
+# low is equally ill-advised since clients could get timeouts even for successful 
+# operations just because the timeout setting is too tight.
+
 # How long the coordinator should wait for read operations to complete
 read_request_timeout_in_ms: 5000
 # How long the coordinator should wait for seq or index scans to complete

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org