[ https://issues.apache.org/jira/browse/CASSANDRA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko updated CASSANDRA-6188: ----------------------------------------- Component/s: Observability > The JMX stats for Speculative Retry stops moving during a node failure outage > period > ------------------------------------------------------------------------------------ > > Key: CASSANDRA-6188 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6188 > Project: Cassandra > Issue Type: Bug > Components: Observability > Environment: One data center of 4 Cassandra-2.0 nodes with default > configuration parameters deployed on 4 separate machines. A testing app (with > either Astyanax or DataStax client driver) interacts with the Cassandra data > center. A traffic generator is sending traffic to the testing app for testing > purpose. > Reporter: Li Zou > Assignee: Ryan McGuire > Priority: Trivial > Fix For: 3.x > > > Under normal testing traffic level with default Cassandra Speculative Retry > configuration for each table (i.e. 99 percentile), JConsole shows that the > JMX stats for Speculative Retry increments slowly. However, during the node > failure outage period (i.e. immediately after the node was killed and before > the gossip figures out that the node is down), JConsole shows that the JMX > stats for Speculative Retry stops moving. That is, for around 20 seconds, the > JMX stats for Speculative Retry does not move. > This is true for all other Speculative Retry options. -- This message was sent by Atlassian JIRA (v6.3.4#6332)