Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Mon, 16 Dec 2013 18:57:08 +0000 (UTC)
From: "Sergey Shelukhin (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12685022.1387220224908.44630.1387220228585@arcas>
In-Reply-To: <JIRA.12685022.1387220224908@arcas>
References: <JIRA.12685022.1387220224908@arcas>
Subject: [jira] [Created] (HBASE-10175) 2-thread ChaosMonkey steps on its
 own toes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sergey Shelukhin created HBASE-10175:
----------------------------------------

             Summary: 2-thread ChaosMonkey steps on its own toes
                 Key: HBASE-10175
                 URL: https://issues.apache.org/jira/browse/HBASE-10175
             Project: HBase
          Issue Type: Improvement
          Components: test
            Reporter: Sergey Shelukhin
            Priority: Minor


ChaosMonkey with one destructive and one volatility (flush-compact-split-etc.) threads steps on its own toes and logs a lot of exceptions.
A simple solution would be to catch most (or all), like NotServingRegionException, and log less (not a full callstack for example, it's not very useful anyway).
A more complicated/complementary one would be to keep track which regions the destructive thread affects and use other regions for volatile one.


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)