[
https://issues.apache.org/jira/browse/CASSANDRA-21190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18087884#comment-18087884
]
Chris Miller commented on CASSANDRA-21190:
------------------------------------------
Thanks [~dipach]
I will confirm client driver details asap.
In the meantime.
The workload type is anomalous and we have implemented application level
changes to handle these in the future. However the 12s timeout error caused a
lot of confusion at the time as we had no parameters set to 12s so its good to
have the background info on this setting. I also think it would be useful to be
able to set this parameter in the cassandra yaml file as it will support others
who might come across this behaviour.
Yes, the anomalous query was executing for > 12s.
Chris,
> 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]
