You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2014/11/22 07:59:35 UTC

[jira] [Updated] (HBASE-11183) Timeline Consistent region replicas - Phase 2 design

     [ https://issues.apache.org/jira/browse/HBASE-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enis Soztutar updated HBASE-11183:
----------------------------------
    Attachment: PhaseIIDesignforHBASE-10070.pdf

A little update is in order. Good news is that, we were able to implement most of the stuff in this second phase design, and get it stable enough and useable (although on an earlier code base based on 0.98). I think, over the following weeks (hopefully), we can get most of the patches in master and resolve the remaining subtasks for HBASE-10070. 

I am attaching an updated design doc, which contains some more details about remaining open tickets under HBASE-10070, esp HBASE-11569, HBASE-11580, HBASE-11842 and memory pressure handling for secondary region replicas. 

> Timeline Consistent region replicas - Phase 2 design
> ----------------------------------------------------
>
>                 Key: HBASE-11183
>                 URL: https://issues.apache.org/jira/browse/HBASE-11183
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>         Attachments: PhaseIIDesignforHBASE-10070.pdf, PhaseIIDesignforHBASE-10070.pdf
>
>
> Now that Phase 1 of parent issue HBASE-10070 is mostly done, it is time to think about remaining items in Phase 2 as per the design doc https://issues.apache.org/jira/secure/attachment/12616659/HighAvailabilityDesignforreadsApachedoc.pdf
> Phase 2 will conclude the work and include at least the following major features: 
>  - Async WAL Replication 
>  - Replication Interface changes (HBASE-10504)
>  - Replication should guarantee seqId order (for region moves and RS failure)
>  - Flush / Compaction events should be written to WAL
>  - Flush / Memstore handling from secondary regions
>  - Region split / merge handling for replicated regions
> In this issue, we can discuss the proposed design, and keep it as like a parent jira for Phase 2 work. We'll open subtasks agains the HBASE-10070 jira for individual patches. 



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