hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-1733) Pluggable replication framework
Date Mon, 12 May 2014 00:33:19 GMT

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

Andrew Purtell resolved HBASE-1733.

    Resolution: Fixed

Addressed closely enough by many other issues

> Pluggable replication framework
> -------------------------------
>                 Key: HBASE-1733
>                 URL: https://issues.apache.org/jira/browse/HBASE-1733
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Replication
>            Reporter: Andrew Purtell
> Put minimal support for replication into core and plan for the rest in contrib/. Support
in core can look like:
> 1. Scope tags in WAL and HCD (HBASE-1728, HBASE-1834). Generic integer, sufficient for
any number of schemes.
> and handled in this issue:
> 2. Method to register remote watchers on WAL rolls, via watcher in ZK. So this is basically
distributed upcall to the listeners on roll. 
> 3. Mechanism to prevent HLog from cleaning rolled logs until all listeners have finished
with it, also implemented with ZK. Could only delete when no more ephemeral subnodes on the
log node, where region server would hold an entry also and delete its entry when edit content
has made it out to the storefiles. 

This message was sent by Atlassian JIRA

View raw message