[
https://issues.apache.org/jira/browse/HBASE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100465#comment-13100465
]
Lars Hofhansl commented on HBASE-2195:
--------------------------------------
Based on a suggestion by Ted I tested the following scenario (with patch v11):
Start with hbase-0.90.x, upgrade and restart with trunk (with 4301 applied),
and set up master-master replication with another trunk cluster. Make sure
replication works fine (and it does)
In terms of versioning...
When we did versioning for a project I used to work on a long time ago, we had
maintained a class version *and* an instance version. We might need both.
The class should know which version it is, but also it is useful in many
scenarios to ask the instance what specific version it is on.
I.e. we need an interface with two methods: One to get the class version, one
to get the instance version.
I think this is for a different patch, though.
> 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
> Assignee: Lars Hofhansl
> Attachments: 2195-v10.txt, 2195-v12.txt, 2195-v13.txt, 2195-v14.txt,
> 2195-v5.txt, 2195-v6.txt, 2195.txt
>
>
> 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
