hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10175) 2-thread ChaosMonkey steps on its own toes
Date Sun, 29 Dec 2013 02:11:50 GMT

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

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

FAILURE: Integrated in HBase-0.98 #40 (See [https://builds.apache.org/job/HBase-0.98/40/])
HBASE-10175. 2-thread ChaosMonkey steps on its own toes (Sergey Shelukhin) (apurtell: rev
1553717)
* /hbase/branches/0.98/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/CompactRandomRegionOfTableAction.java
* /hbase/branches/0.98/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/CompactTableAction.java
* /hbase/branches/0.98/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/FlushRandomRegionOfTableAction.java
* /hbase/branches/0.98/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/FlushTableAction.java
* /hbase/branches/0.98/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/MergeRandomAdjacentRegionsOfTableAction.java
* /hbase/branches/0.98/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/MoveRegionsOfTableAction.java
* /hbase/branches/0.98/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)

Mime
View raw message