Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 714A710828 for ; Wed, 10 Jul 2013 23:19:48 +0000 (UTC) Received: (qmail 75620 invoked by uid 500); 10 Jul 2013 23:19:48 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 75564 invoked by uid 500); 10 Jul 2013 23:19:48 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 75389 invoked by uid 99); 10 Jul 2013 23:19:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 23:19:48 +0000 Date: Wed, 10 Jul 2013 23:19:48 +0000 (UTC) From: "Sergey Shelukhin (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-8923) ChaosMonkey test teardown may fail due to race with ChaosMonkey 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/HBASE-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-8923: ------------------------------------ Priority: Minor (was: Major) > ChaosMonkey test teardown may fail due to race with ChaosMonkey > --------------------------------------------------------------- > > Key: HBASE-8923 > URL: https://issues.apache.org/jira/browse/HBASE-8923 > Project: HBase > Issue Type: Bug > Components: test > Affects Versions: 0.98.0, 0.95.1, 0.94.9 > Reporter: Sergey Shelukhin > Assignee: Sergey Shelukhin > Priority: Minor > Fix For: 0.95.2, 0.94.10 > > Attachments: HBASE-8923-v0-94.patch, HBASE-8923-v0.patch > > > If chaosmonkey restarts RS at the last moment before test teardown happens, cluster recovery may not see it in cluster status; however, RS process is already running, so when cluster recovery also tries to start it, it gets ExitCodeException. Boom! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira