Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 11 Oct 2013 22:26:43 +0000 (UTC)
From: "Li Zou (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12673503.1381530376116.54124.1381530403628@arcas>
In-Reply-To: <JIRA.12673503.1381530376116@arcas>
References: <JIRA.12673503.1381530376116@arcas>
Subject: [jira] [Created] (CASSANDRA-6188) The JMX stats for Speculative
 Retry stops moving during a node failure outage period
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Li Zou created CASSANDRA-6188:
---------------------------------

             Summary: 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: Core
         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


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.1#6144)