You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2014/09/08 13:14:29 UTC

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

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

ramkrishna.s.vasudevan commented on HBASE-11367:
------------------------------------------------

[~enis]
Do you think it is possible to back port this to 0.98? 

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