[
https://issues.apache.org/jira/browse/HBASE-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745664#comment-14745664
]
Matteo Bertozzi commented on HBASE-14362:
-----------------------------------------
if you look at the TestWALProcedureStoreOnHDFS code it already say that is
flaky in case of slow machines.
you can bump the value as much as you want, but if the machine is even slower
it will fail again.
the other downside is that it will slow down runs on faster machines
{code}
// increase the value for slow test-env
conf.setInt("hbase.procedure.store.wal.wait.before.roll", 1000);
conf.setInt("hbase.procedure.store.wal.max.roll.retries", 5);
conf.setInt("hbase.procedure.store.wal.sync.failure.roll.max", 5);
{code}
> org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS is super
> duper flaky
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-14362
> URL: https://issues.apache.org/jira/browse/HBASE-14362
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 2.0.0
> Reporter: Dima Spivak
> Priority: Critical
>
> [As seen in
> Jenkins|https://builds.apache.org/job/HBase-TRUNK/lastCompletedBuild/testReport/org.apache.hadoop.hbase.master.procedure/TestWALProcedureStoreOnHDFS/history/],
> this test has been super flaky and we should probably address it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
