[
https://issues.apache.org/jira/browse/CASSANDRA-21190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18087861#comment-18087861
]
Dipankar Achinta commented on CASSANDRA-21190:
----------------------------------------------
[~chrisjmiller] Before considering whether exposing _native_transport_timeout_
*__* via {{cassandra.yaml}} would help in this case, could you please confirm
which Cassandra driver and version is being used, and whether a driver-side
request/read timeout has been explicitly configured?
Also could you help understand below,
* What is the workload type that exceeds this 12 sec timeout and whether it is
unavoidable ?
* Is the request actually spending time queued on the coordinator, or is it
executing for >12s ?
> 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]
