Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 23 Oct 2015 15:53:27 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12858618.1440508880000.41295.1445615607732@Atlassian.JIRA>
In-Reply-To: <JIRA.12858618.1440508880000@Atlassian.JIRA>
References: <JIRA.12858618.1440508880000@Atlassian.JIRA>
 <JIRA.12858618.1440508880089@arcas>
Subject: [jira] [Updated] (CASSANDRA-10175) cassandra-stress should be
 tolerant when a remote node shutdown
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-10175:
------------------------------------------
    Issue Type: Improvement  (was: Bug)

> cassandra-stress should be tolerant when a remote node shutdown 
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-10175
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10175
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Alan Boudreault
>             Fix For: 3.x
>
>
> Currently, if we start a stress session with 3 nodes and shutdown one node, stress will crash. It is caused by the JMX connection lost on the node, which is use to collect some gc stats IIRC. 
> backtrace: https://gist.github.com/aboudreault/6cd82bb0acc681992414
> Stress should handle that jmx connection lost in a better way so the session could continue. Ideally, it should try to *reconnect* to JMX if the node is back online?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)