hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18146) Long running integration test similar to TestAcidGuarantees
Date Fri, 02 Jun 2017 00:44:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033977#comment-16033977
] 

Jonathan Hsieh commented on HBASE-18146:
----------------------------------------

Ugh, I realize that was hard to understand/parse but I think you got the jist.  -- An alternative
would be to change the flush size config.  

That said, a monkeyfactory that flushes frequently and causes compactions frequently (and
similarly, a split/merge monkey factory) make sense.  Would it make sense to just file those
as separate tickets? We coudl also either close this out as info provided or convert it to
a docs improvement jira?)

> 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)

Mime
View raw message