[
https://issues.apache.org/jira/browse/CASSANDRA-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313585#comment-14313585
]
Pramod Nair commented on CASSANDRA-8595:
----------------------------------------
I investigated this timeout scenario by bringing down some nodes manually in my
C* cluster, and trying a read or write with consistency level set to ALL, but
couldn't capture the endpoints which went down.
I could only capture the total no. of endpoints/nodes involved in the reading
process.
I need some help here, as in how to capture info about down or unresponsive
nodes.
> Emit timeouts per endpoint
> --------------------------
>
> Key: CASSANDRA-8595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8595
> Project: Cassandra
> Issue Type: Improvement
> Reporter: sankalp kohli
> Priority: Minor
>
> We currently emit number of timeouts experienced by a co-ordinator while
> doing reads and writes. This does not tell us which replica or endpoint is
> responsible for the timeouts.
> We can keep a map of endpoint to number of timeouts which could be emitted
> via JMX.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
