[ 
https://issues.apache.org/jira/browse/HBASE-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858227#comment-13858227
 ] 

Hudson commented on HBASE-10175:
--------------------------------

SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-1.1 #27 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-1.1/27/])
HBASE-10175 2-thread ChaosMonkey steps on its own toes (sershe: rev 1553634)
* 
/hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/CompactRandomRegionOfTableAction.java
* 
/hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/CompactTableAction.java
* 
/hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/FlushRandomRegionOfTableAction.java
* 
/hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/FlushTableAction.java
* 
/hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/MergeRandomAdjacentRegionsOfTableAction.java
* 
/hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/MoveRegionsOfTableAction.java
* 
/hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/SplitRandomRegionOfTableAction.java


> 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
>            Assignee: Sergey Shelukhin
>            Priority: Minor
>             Fix For: 0.98.0, 0.99.0
>
>         Attachments: HBASE-10175.patch
>
>
> 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.5#6160)

Reply via email to