maedhroz commented on code in PR #3274:
URL: https://github.com/apache/cassandra/pull/3274#discussion_r1591501158
##########
src/java/org/apache/cassandra/config/Config.java:
##########
@@ -1283,4 +1283,21 @@ public static void log(Config config)
public double severity_during_decommission = 0;
public StorageCompatibilityMode storage_compatibility_mode;
+
+ public enum CQLStartTime
+ {
+ REQUEST, // uses a timestamp that represent the start of processing of
the request
+ QUEUE // uses a timestamp that represents when the request was
enqueued
+ }
+ public volatile CQLStartTime cql_start_time = CQLStartTime.REQUEST;
+
+ public boolean native_transport_throw_on_overload = false;
+ public double native_transport_queue_max_item_age_threshold =
Double.MAX_VALUE;
+ public DurationSpec.LongMillisecondsBound
native_transport_min_backoff_on_queue_overload = new
DurationSpec.LongMillisecondsBound("10ms");
+ public DurationSpec.LongMillisecondsBound
native_transport_max_backoff_on_queue_overload = new
DurationSpec.LongMillisecondsBound("200ms");
+
+ // 3.0 Cassandra Driver has its "read" timeout set to 12 seconds. Our
recommendation is match this. Default is 100 seconds, which is extremely high
+ // but still not completely unbounded.
+ public DurationSpec.LongMillisecondsBound native_transport_timeout = new
DurationSpec.LongMillisecondsBound("100000ms");
Review Comment:
This default is likely moving to something lower, at least from what I'm
reading in the Jira? Is there any reference value in anything else on the
classpath, or do we kind of just have to hard-code something w/ out-of-band
knowledge. Do we want to use something like 20, 30...or go all the way to 12.
Also, which of these, if any, do we want to document in `cassandra.yaml`?
I'm okay w/ leaving things out that we really don't operators should change...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
