[
https://issues.apache.org/jira/browse/HBASE-18651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176137#comment-16176137
]
Hudson commented on HBASE-18651:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3757 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3757/])
HBASE-18651 Let ChaosMonkeyRunner expose the chaos monkey runner it (mdrob: rev
5f238b3ef46e7d5f31a9fb2dfff0111085af835d)
* (add)
hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestMonkeys.java
* (edit)
hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/util/ChaosMonkeyRunner.java
* (add) hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/util/Monkeys.java
> 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)
