[
https://issues.apache.org/jira/browse/HBASE-18146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033556#comment-16033556
]
Jonathan Hsieh commented on HBASE-18146:
----------------------------------------
IntegrationTestAcidGuarantees works against real clusters for a configurable
amount of time. See:
https://github.com/apache/hbase/blob/master/hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestAcidGuarantees.java#L113
This can be done via the command line like so:
hbase org.apache.hadoop.hbase.IntegrationTestAcidGuarantees -DnumWriters=5
-DnumGetters=1 -DnumScanners=1 -Dmillis=600000 -m calm
In some internal setups, we've been running it against multiple branches for 10
minute runs with each monkey enabled against various configuration settings
(e.g. all writes through multiwal, through mob write path, under kerberos
security etc).
> 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)
