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

Posted to issues@hbase.apache.org by "Reid Chan (JIRA)" <ji...@apache.org> on 2017/09/04 10:31:02 UTC

[jira] [Commented] (HBASE-18651) Let ChaosMonkeyRunner expose the chaos monkey runner it creates

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

Reid Chan commented on HBASE-18651:
-----------------------------------

First version is based on my comprehension about the discussion in HBASE-18629 (not quite sure if it is as expected...
Need some suggestions, thank you [~tedyu]

> 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
>         Attachments: HBASE-18651.master.001.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)