hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11183) Timeline Consistent region replicas - Phase 2 design
Date Fri, 23 May 2014 01:18:02 GMT

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

Mikhail Antonov commented on HBASE-11183:

Interesting reading!

bq. The secondary serves reads from 
a merged view of primary's store files, secondary's memstore and secondary's spill file (which 
would be yet another storefile)

"Yet another store file" means that's it's file in local FS, but just in format of store file?

bq. Though as already 
reported elsewhere, region moves and failures can cause concurrent or out­of­order delivery of 
wal edits to the receiving side
Is that what happens now in this case for general replication queue, as I understand? out
of order delivery of edits, how is it handled in receiving side?

What are the numbers for replication queue source failover time (compared for example with
the ones for RS failover currently - bounded by ZK timeout)?

> 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
> 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

View raw message