[
https://issues.apache.org/jira/browse/CASSANDRA-21190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18088022#comment-18088022
]
Dipankar Achinta commented on CASSANDRA-21190:
----------------------------------------------
Appreciate the details shared.
I'm not aware of the historical context behind the decision not to expose this
property as a tunable. Based on the information shared, the workload that
uncovered this behavior appears to be anomalous. In that context, the current
default ({_}12 secs{_}) seems to provide reasonable headroom for the vast
majority of workloads.
Given that this property has existed for quite some time without being exposed,
it would be useful to understand whether there are broader, valid use cases
that would benefit from tuning it beyond the default. Without that, I'm not
sure there's a strong case for making it an operator facing configuration knob.
That said, I'll defer to others who may have more historical context on the
original design decision and any operational considerations around exposing it.
Thanks.
> Seeing timeout 11999 msec/cross-node but how to change the associated
> parameter
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-21190
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21190
> Project: Apache Cassandra
> Issue Type: Bug
> Reporter: Chris Miller
> Priority: Urgent
>
> Hi folks,
> We're seeing timeouts such as the following on our production system and need
> to increase the associated parameter (but there doesn't seem to be an
> equivalent parameter). Any ideas how to increase the 11999 msec timeout.
> <SELECT ..., total time 12003 msec, timeout 11999 msec/cross-node
> Cassandra version: 4.1.6
> Thanks,
> Chris.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
