[
https://issues.apache.org/jira/browse/HBASE-13154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348268#comment-14348268
]
Jonathan Hsieh commented on HBASE-13154:
----------------------------------------
[~anoop.hbase], I'm a little confused by your comment.
Setting -DuseMob makes checks to make sure hfile v3 is being used and either
creates a the new table or uses the existing table and then modifies the first
cf such that the mob threshold is 4 and mob is enabled.
For example, to run the integration test in a mode that exercises the mob
feature, I use this command line (where RUNMS and MONKEY are set).
{code}
$HBASE_HOME/bin/hbase org.apache.hadoop.hbase.IntegrationTestAcidGuarantees
-DuseMob=true -Dmillis=$RUNMS -m $MONKEY
{code}
> Add support for mob in TestAcidGuarantees and IntegrationTestAcidGuarantees
> ---------------------------------------------------------------------------
>
> Key: HBASE-13154
> URL: https://issues.apache.org/jira/browse/HBASE-13154
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests, mob
> Affects Versions: hbase-11339
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Fix For: hbase-11339
>
> Attachments: hbase-13154.patch
>
>
> Adding support to run acid guarantees tests on data that is primarily in the
> mob path.
> We essentially set the mob size to be very small (4) and run the same test.
> This is activated using the -DuseMob=true tool style command line arg.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
