hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-18651) Let ChaosMonkeyRunner expose the chaos monkey runner it creates
Date Fri, 22 Sep 2017 02:43:00 GMT

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

Mike Drob updated HBASE-18651:
------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0-alpha-4
                   3.0.0
           Status: Resolved  (was: Patch Available)

> Let ChaosMonkeyRunner expose the chaos monkey runner it creates
> ---------------------------------------------------------------
>
>                 Key: HBASE-18651
>                 URL: https://issues.apache.org/jira/browse/HBASE-18651
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Reid Chan
>             Fix For: 3.0.0, 2.0.0-alpha-4
>
>         Attachments: HBASE-18651.master.001.patch, HBASE-18651.master.002.patch, HBASE-18651.master.003.patch,
HBASE-18651.master.004.patch, HBASE-18651.master.005.patch, HBASE-18651.master.006.patch
>
>
> Currently ChaosMonkeyRunner#main() instantiates ChaosMonkeyRunner without keeping track
of the instance.
> This poses some challenge when ChaosMonkeyRunner is used programmatically because the
caller cannot get hold of the runner.
> As [~mdrob] suggested, we should expose the chaos monkey runner.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message