[
https://issues.apache.org/jira/browse/HBASE-11992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135909#comment-14135909
]
Andrew Purtell edited comment on HBASE-11992 at 9/16/14 6:33 PM:
-----------------------------------------------------------------
I also wonder about service migration when upgrading from 0.98 to 1.0, which is
supposed to be wire compatible and should have the same mixed-version
deployment tolerance as 0.98. In order to stage in customized replication
endpoints do we require remove_peer then add_peer, instead of an online
migration and update of existing replication sources? The former implies
service downtime or some edits that should have been replicated will be missed
between remove and (re)add, the latter does not.
was (Author: apurtell):
I also wonder about major service migration. In order to stage in customized
replication endpoints do we require remove_peer then add_peer, instead of an
online migration and update of existing replication sources? The former implies
service downtime or some edits that should have been replicated will be missed
between remove and (re)add, the latter does not.
> Backport HBASE-11367 (Pluggable replication endpoint) to 0.98
> -------------------------------------------------------------
>
> Key: HBASE-11992
> URL: https://issues.apache.org/jira/browse/HBASE-11992
> Project: HBase
> Issue Type: Task
> Reporter: Andrew Purtell
> Assignee: ramkrishna.s.vasudevan
> Attachments: hbase-11367_0.98.patch
>
>
> ReplicationSource tails the logs for each peer. HBASE-11367 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 issue is for backporting HBASE-11367 to 0.98.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
