[
https://issues.apache.org/jira/browse/HBASE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819694#comment-13819694
]
Lars Hofhansl commented on HBASE-9934:
--------------------------------------
Fixed the comment :)
OK I get it, each source-sink pair has to be declared to only do one hop. Hmm.
As you said it makes sense to expose this via addPeer. Then where to put this
information? Maybe in ZK. Then we need to a good way to check that information
when it is time to replicate at the sink for that data. Maybe it's not quite as
simple as I thought.
Do you have time to work up a patch [~ishanc]?
> Mesh replication (a.k.a. multi master replication)
> --------------------------------------------------
>
> Key: HBASE-9934
> URL: https://issues.apache.org/jira/browse/HBASE-9934
> Project: HBase
> Issue Type: New Feature
> Components: Replication
> Reporter: Ishan Chhabra
> Priority: Minor
>
> This is to setup NxN replication.
> See background discussion here:
> http://mail-archives.apache.org/mod_mbox/hbase-user/201311.mbox/%3CCAOiuM-4UMmLA7UHMp4hhjpLWUrHDxg1t4tN4aWvnZUMcTxG%2BKQ%40mail.gmail.com%3E
> We can add a new mode in replication to not forward edits from other
> clusters. Not sure what should be done when some clusters are configured with
> this setting and some aren't.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
