[
https://issues.apache.org/jira/browse/HBASE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095126#comment-13095126
]
stack commented on HBASE-2195:
------------------------------
Adding clusterid to the attribute map seems fine though it probably be more
efficient having clusterid a native data member on Put and Delete.
Current ClusterId is UUID (See MasterFileSystem where its written). It takes
128bits to represent uuid in bits only. Is that too much per edit to carry
replicating? It'd for sure be 'safe' such that cluster ids would never 'clash'
because someone messed up the mappings of clusterid to some short form.
> Support cyclic replication
> --------------------------
>
> Key: HBASE-2195
> URL: https://issues.apache.org/jira/browse/HBASE-2195
> Project: HBase
> Issue Type: Sub-task
> Components: replication
> Reporter: Jean-Daniel Cryans
>
> We need to support cyclic replication by using the cluster id of each HlogKey
> and stop replicating when it goes back to the original cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
