[
https://issues.apache.org/jira/browse/HBASE-17081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762215#comment-15762215
]
Anastasia Braginsky commented on HBASE-17081:
---------------------------------------------
[~anoop.hbase], [~ram_krish], TestAsyncGetMultiThread doesn't fail with
HBASE-17294 only. HBASE-17294 was committed after it passed all tests including
TestAsyncGetMultiThread. Also now when Eshcar is trying TestAsyncGetMultiThread
on her patch solely it passes. So it must be some specific interleaving between
HBASE-17294 and HBASE-17081 that causes the problem.
[[email protected]], when you see TestAsyncGetMultiThread passing without my
patch is it with HBASE-17294 or without?
> Flush the entire CompactingMemStore content to disk
> ---------------------------------------------------
>
> Key: HBASE-17081
> URL: https://issues.apache.org/jira/browse/HBASE-17081
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anastasia Braginsky
> Assignee: Anastasia Braginsky
> Attachments: HBASE-15787_8.patch, HBASE-17081-V01.patch,
> HBASE-17081-V02.patch, HBASE-17081-V03.patch, HBASE-17081-V04.patch,
> HBASE-17081-V05.patch, HBASE-17081-V06.patch, HBASE-17081-V06.patch,
> HBASE-17081-V07.patch, HBaseMeetupDecember2016-V02.pptx,
> Pipelinememstore_fortrunk_3.patch
>
>
> Part of CompactingMemStore's memory is held by an active segment, and another
> part is divided between immutable segments in the compacting pipeline. Upon
> flush-to-disk request we want to flush all of it to disk, in contrast to
> flushing only tail of the compacting pipeline.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
