hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17373) Reverse the order of snapshot creation in the CompactingMemStore
Date Mon, 02 Jan 2017 05:28:58 GMT

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

ramkrishna.s.vasudevan commented on HBASE-17373:
------------------------------------------------

Before reviewing the patch,
WAs the issue in the TestAsync* test case due to the lack of synchronization issue only and
solving that itself can solve this problem? Or is it two different problems that we have ?
Just asking.

> Reverse the order of snapshot creation in the CompactingMemStore
> ----------------------------------------------------------------
>
>                 Key: HBASE-17373
>                 URL: https://issues.apache.org/jira/browse/HBASE-17373
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Anastasia Braginsky
>            Assignee: Eshcar Hillel
>         Attachments: HBASE-17373-V01.patch, HBASE-17373-V02.patch, HBASE-17373-V03.patch
>
>
> In CompactingMemStore both in BASIC and EAGER cases when snapshot is created the segments
are first removed from the pipeline then added to the snapshot. This is the opposite to what
is done in the DefaultMemStore where the snapshot is firstly created with the active segment
and only after the active segment is refreshed. This JIRA is about to reverse the order in
CompactingMemStore and to make all MemStores to behave the same.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message