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

Posted to dev@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2013/12/16 19:57:08 UTC

[jira] [Created] (HBASE-10175) 2-thread ChaosMonkey steps on its own toes

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)