You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/08/25 16:55:46 UTC

[jira] [Updated] (CASSANDRA-10175) cassandra-stress should be tolerant when a remote node shutdown

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

Jonathan Ellis updated CASSANDRA-10175:
---------------------------------------
    Issue Type: Bug  (was: Improvement)

> 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: Bug
>            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)