[
https://issues.apache.org/jira/browse/HBASE-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705623#comment-13705623
]
gautam commented on HBASE-8928:
-------------------------------
Yes, for CM I will post the changes for review. For Policies I was trying to
add Periodic Sequential policy, which at the moment I cant see.
For LoadTestTool, I wanted to relax the verification criteria as I have
observed that even if 1 write has failed out of say 1 million write operations,
the test fails. I wanted to move it to percentile for the new actions where I
will be using this framework.
> Make ChaosMonkey & LoadTest tools extensible, to allow addition of more
> actions and policies.
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-8928
> URL: https://issues.apache.org/jira/browse/HBASE-8928
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 0.95.2
> Reporter: gautam
> Assignee: Enis Soztutar
>
> Let me split this requirement into 2 parts:
> i) ChaosMonkey
> I was trying to add more tests around new actions and policies by leveraging
> the existing classes nested inside ChaosMonkey.
> But it turned out that some of the classes cannot be used outside, unless we
> make those visible to the world.
> Here is an example:
> I cannot extend ChaosMonkey.Action, as the init(ActionContext context) method
> has package-wide visibility.
> There are other places as well which makes it impossible for anyone to extend
> on top of this hierarchy.
> ii) LoadTestTool
> I wanted to extend this tool to define failure/pass criteria based on % of
> read/write failed, rather than comparing against absolute 0.
> For that this beautiful class should mark some of its properties usable by
> its child, by marking those protected.
> I wanted to get unblocked here first.
> Once this gets fixed, I think I can take up a JIRA item to refactor these
> tools, if required.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
