[
https://issues.apache.org/jira/browse/HBASE-18610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142043#comment-16142043
]
Ted Yu commented on HBASE-18610:
--------------------------------
This was the command I used on docker where 227 is the directory holding
hbase-site.xml pointing to remote cluster:
{code}
./buck-out/gen/core/load-client --num_rows=200 --num_cols=3 --table=t
--families=d --appends=false -monkey=serverKilling -conf 227
{code}
In the output, I saw:
{code}
2017-08-25 19:00:34,505 INFO [main-SendThread(172.26.109.228:2181)]
zookeeper.ClientCnxn (ClientCnxn.java:onConnected(1299)) - Session
establishment complete on server 172.26.109.228/172.26.109.228:2181, sessionid
= 0x25d2dc12805569e, negotiated timeout = 40000
2017-08-25 19:00:34,567 INFO [main] policies.Policy
(PeriodicPolicy.java:init(57)) - Using ChaosMonkey Policy: class
org.apache.hadoop.hbase.chaos.policies.DoActionsOncePolicy, period: 60000
2017-08-25 19:00:34,568 INFO [main] policies.Policy
(PeriodicPolicy.java:init(57)) - Using ChaosMonkey Policy: class
org.apache.hadoop.hbase.chaos.policies.PeriodicRandomActionPolicy, period: 60000
2017-08-25 19:00:34,569 INFO [main] policies.Policy
(PeriodicPolicy.java:init(57)) - Using ChaosMonkey Policy: class
org.apache.hadoop.hbase.chaos.policies.PeriodicRandomActionPolicy, period: 60000
{code}
You need to rebuild hbase-it module so that recent change to ChaosMonkeyRunner
can be picked up.
> Provide capability to activate chaos monkey
> -------------------------------------------
>
> Key: HBASE-18610
> URL: https://issues.apache.org/jira/browse/HBASE-18610
> Project: HBase
> Issue Type: Sub-task
> Reporter: Ted Yu
> Attachments: 18610.v1.txt, 18610.v4.txt, 18610.v5.txt
>
>
> Currently load-client runs against a cluster where region servers are stable.
> We need to introduce chaos monkey so that wider coverage for read path is
> exercised.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)