hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11367) Pluggable replication endpoint
Date Tue, 09 Sep 2014 06:24:30 GMT

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

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

There are few changes to the ReplicationPeer and ReplicationPeers interface though they are
marked private is it ok to change the interface in 0.98.7 releases? In general what could
be the best policy that could  be applied here?  May be I can see if there is anyother different
way to do it but just asking this because after we back port it in 0.98.7 again in 1.0 it
should not have different interface APIs.

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

Mime
View raw message