hbase-issues mailing list archives

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

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

Eshcar Hillel commented on HBASE-17373:
---------------------------------------

These are two different problems.
Here the problem was removing the segments from pipeline before adding them to the snapshot.
HBASE-17379 handles a synchronization problem that causes a concurrent-modification-exception.

Both exist in trunk.

> 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,
HBASE-17373-V04.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