You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nicholas Jiang (Jira)" <ji...@apache.org> on 2019/09/10 09:08:00 UTC

[jira] [Commented] (HBASE-14413) Procedure V2 - Snapshot V2

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

Nicholas Jiang commented on HBASE-14413:
----------------------------------------

[~openinx]https://docs.google.com/document/d/1Gy6fJtf6IA3IB_EtQcGhjwVB3U8mCnVnHB3sYwKI5KU/edit?usp=sharing,I have designed snapshot implementation  based on Procedure V2 framework.Can you review this?

> Procedure V2 - Snapshot V2
> --------------------------
>
>                 Key: HBASE-14413
>                 URL: https://issues.apache.org/jira/browse/HBASE-14413
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Vladimir Rodionov
>            Assignee: Zheng Hu
>            Priority: Major
>
> We need new implementation of snapshot feature that is more robust and performant.  Ideally, it will work with multiple tables as well. The possible areas of improvements:
> #  Must be flushless. Coordinated memstore flushes across a cluster are bad.
> #  Verification phase must be distributed, done in parallel and not on Master.
> In theory, the only info we need to record snapshot of a table: list of WAL files, list of HFiles and max sequence id of an edit which has been flushed per Region.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)