[
https://issues.apache.org/jira/browse/HBASE-19288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258204#comment-16258204
]
Chia-Ping Tsai commented on HBASE-19288:
----------------------------------------
The HBASE-16417 reduces the threshold of in-memory flush, hence the extra
in-memory flush may be executed before we evaluate the count.
{code}
Setting in-memory flush size threshold to 10
{code}
[~tedyu] Could you please add the following config to increase the threshold?
The {{0.25}} is the previous setting.
{code}
conf.set(CompactingMemStore.IN_MEMORY_FLUSH_THRESHOLD_FACTOR_KEY,
String.valueOf(0.25));
{code}
> Intermittent test failure in TestHStore.testRunDoubleMemStoreCompactors
> -----------------------------------------------------------------------
>
> Key: HBASE-19288
> URL: https://issues.apache.org/jira/browse/HBASE-19288
> Project: HBase
> Issue Type: Test
> Components: test
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 2.0.0-beta-1
>
> Attachments: 19288.v1.txt, testRunDoubleMemStoreCompactors.out
>
>
> Here was one of the test failures:
> https://builds.apache.org/job/PreCommit-HBASE-Build/9812/testReport/junit/org.apache.hadoop.hbase.regionserver/TestHStore/testRunDoubleMemStoreCompactors/
>
> {code}
> [ERROR]
> org.apache.hadoop.hbase.regionserver.TestHStore.testRunDoubleMemStoreCompactors(org.apache.hadoop.hbase.regionserver.TestHStore)
> [ERROR] Run 1: TestHStore.testRunDoubleMemStoreCompactors:1500 expected:<2>
> but was:<3>
> [ERROR] Run 2: TestHStore.testRunDoubleMemStoreCompactors:1481 expected:<1>
> but was:<4>
> [ERROR] Run 3: TestHStore.testRunDoubleMemStoreCompactors:1481 expected:<1>
> but was:<5>
> {code}
> From the counts for second and third runs, we know that RUNNER_COUNT was not
> cleared in between the reruns, leading to failure at the 1st assertion.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)