[
https://issues.apache.org/jira/browse/HBASE-18146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033884#comment-16033884
]
Jonathan Hsieh commented on HBASE-18146:
----------------------------------------
There is always room for improvement. :) For your initial specific asks, I
think this is sufficient.
That suggested monkey sounds useful. An alternative appraoch that would
require config as opposed to code woudl be to flush size on the cluster under
test which would to exercise flush and compact those mechanisms more frequently
(would affect a few of my other favorites like ITBLL and ITIngest)
The fact that this was filed means we should probably add a section to the docs
to make it more obvious that this and other tests are runnable from the command
line. (some IT tests use the class's static main function to run, other use
the ITDriver to execute some canned runs).
> Long running integration test similar to TestAcidGuarantees
> -----------------------------------------------------------
>
> Key: HBASE-18146
> URL: https://issues.apache.org/jira/browse/HBASE-18146
> Project: HBase
> Issue Type: Test
> Components: integration tests
> Reporter: Andrew Purtell
>
> TestAcidGuarantees and IntegrationTestAcidGuarantees both really only work
> with minicluster based testing and do not run for a long duration. Consider a
> new integration test that makes similar atomicity checks while running for,
> potentially, a very long time, determined by test parameters supplied on the
> command line (perhaps as property definitions). The new integration test
> should expect to run against a distributed cluster, support specification of
> desired monkey policy, and not require any special non-default site
> configuration settings.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
