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/09/16 08:58:36 UTC

[jira] [Updated] (HBASE-11367) Pluggable replication endpoint

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

Enis Soztutar updated HBASE-11367:
----------------------------------
    Attachment: hbase-11367_0.98.patch

Attaching a backported 0.98 patch which should apply on top of 0.98.4 or so. This can be used as a base for a backport jira if we want to do it. 

> Pluggable replication endpoint
> ------------------------------
>
>                 Key: HBASE-11367
>                 URL: https://issues.apache.org/jira/browse/HBASE-11367
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>            Priority: Blocker
>             Fix For: 0.99.0, 2.0.0
>
>         Attachments: 0001-11367.patch, hbase-11367_0.98.patch, hbase-11367_v1.patch, hbase-11367_v2.patch, hbase-11367_v3.patch, hbase-11367_v4.patch, hbase-11367_v4.patch, hbase-11367_v5.patch
>
>
> We need a pluggable endpoint for replication for more flexibility. See parent jira for more context. 
> ReplicationSource tails the logs for each peer. This jira introduces ReplicationEndpoint which is customizable per peer. ReplicationEndpoint is run in the same RS process and instantiated per replication peer per region server. Implementations of this interface handle the actual shipping of WAL edits to the remote cluster. 



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