Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 295F918681 for ; Tue, 25 Aug 2015 14:55:48 +0000 (UTC) Received: (qmail 55932 invoked by uid 500); 25 Aug 2015 14:55:46 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 55721 invoked by uid 500); 25 Aug 2015 14:55:46 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 55583 invoked by uid 99); 25 Aug 2015 14:55:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Aug 2015 14:55:46 +0000 Date: Tue, 25 Aug 2015 14:55:46 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-10175: --------------------------------------- Assignee: Benedict > 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 > Assignee: Benedict > 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)