[
https://issues.apache.org/jira/browse/HBASE-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800821#action_12800821
]
Jean-Daniel Cryans commented on HBASE-2129:
-------------------------------------------
@Andrew
The way I plan it, every region server can support both a ReplicationSource and
a ReplicationSink. With the right configuration in zookeeper, you could easily
get a master-master setup but also a chain of replication (cluster A replicates
to cluster B which replicates to cluster C). In the case of master/master, you
have to manage to not replicate edits from which you are the origin (I know you
know that). I guess you could encode that information in KV (routing
information?).
WRT scoping, I left it out of this particular Jira but it is one of the next
item on my todo list along with live configuration of replication streams and
being able to ask a cluster to replicate edits from time X (which is partly
enabled by HBASE-2070).
> Simple Master/Slave replication
> -------------------------------
>
> Key: HBASE-2129
> URL: https://issues.apache.org/jira/browse/HBASE-2129
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Fix For: 0.21.0
>
> Attachments: HBASE-2129.patch
>
>
> We should first build a very simple replication mechanism to validate our
> assumptions and get a feel of what replication is in this very distributed
> context.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
