You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2013/12/20 02:42:07 UTC

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

     [ https://issues.apache.org/jira/browse/HBASE-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Shelukhin updated HBASE-10175:
-------------------------------------

    Status: Patch Available  (was: Open)

> 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
>         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.4#6159)