[
https://issues.apache.org/jira/browse/HBASE-18146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033919#comment-16033919
]
Andrew Purtell commented on HBASE-18146:
----------------------------------------
bq. An alternative appraoch that would require config as opposed to code woudl
be to flush size on the cluster under test
That's what I was getting at earlier when suggesting the test shouldn't depend
on changes to deployed site configuration, and how the current test seems
limited.
> 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)
