You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by be...@apache.org on 2021/09/30 05:50:10 UTC
[cassandra] branch cassandra-4.0 updated (5d457bc -> 42905e9)
This is an automated email from the ASF dual-hosted git repository.
bereng pushed a change to branch cassandra-4.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git.
from 5d457bc Merge branch 'cassandra-3.11' into cassandra-4.0
new 7c067b6 Add indication in cassandra.yaml that rpc timeouts going too high will cause memory build up
new 42905e9 Merge branch 'cassandra-3.11' into cassandra-4.0
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
conf/cassandra.yaml | 13 +++++++++++++
1 file changed, 13 insertions(+)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-3.11' into cassandra-4.0
Posted by be...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
bereng pushed a commit to branch cassandra-4.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit 42905e94b52f5c88be78e3224a646bfec6f100c4
Merge: 5d457bc 7c067b6
Author: Bereng <be...@gmail.com>
AuthorDate: Thu Sep 30 07:46:16 2021 +0200
Merge branch 'cassandra-3.11' into cassandra-4.0
conf/cassandra.yaml | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --cc conf/cassandra.yaml
index 46d94d9,48bf0b4..2af8fc4
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@@ -893,21 -852,29 +893,34 @@@ sstable_preemptive_open_interval_in_mb
# 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
+# How long the coordinator should wait for read operations to complete.
+# Lowest acceptable value is 10 ms.
read_request_timeout_in_ms: 5000
-# How long the coordinator should wait for seq or index scans to complete
+# How long the coordinator should wait for seq or index scans to complete.
+# Lowest acceptable value is 10 ms.
range_request_timeout_in_ms: 10000
-# How long the coordinator should wait for writes to complete
+# How long the coordinator should wait for writes to complete.
+# Lowest acceptable value is 10 ms.
write_request_timeout_in_ms: 2000
-# How long the coordinator should wait for counter writes to complete
+# How long the coordinator should wait for counter writes to complete.
+# Lowest acceptable value is 10 ms.
counter_write_request_timeout_in_ms: 5000
# How long a coordinator should continue to retry a CAS operation
-# that contends with other proposals for the same row
+# that contends with other proposals for the same row.
+# Lowest acceptable value is 10 ms.
cas_contention_timeout_in_ms: 1000
# How long the coordinator should wait for truncates to complete
# (This can be much longer, because unless auto_snapshot is disabled
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org