[
https://issues.apache.org/jira/browse/HBASE-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-7158:
---------------------------------
Description:
When I worked on HBASE-2195 I added a mechanism for an edit to identify its
source cluster, so that replication would not bounce it back to the source.
See: {{this.clusterId =
zkHelper.getUUIDForCluster(zkHelper.getZookeeperWatcher());}} in
ReplicationSource, and {{put.setClusterId(entry.getKey().getClusterId());}} in
ReplicationSink.
In master-master replication scenarios, it would very useful if CopyTable would
identify the source cluster (by tagging each Put/Delete with the source
clusterId before applying it).
> Allow CopyTable to identify the source cluster (for replication scenarios)
> --------------------------------------------------------------------------
>
> Key: HBASE-7158
> URL: https://issues.apache.org/jira/browse/HBASE-7158
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
>
> When I worked on HBASE-2195 I added a mechanism for an edit to identify its
> source cluster, so that replication would not bounce it back to the source.
> See: {{this.clusterId =
> zkHelper.getUUIDForCluster(zkHelper.getZookeeperWatcher());}} in
> ReplicationSource, and {{put.setClusterId(entry.getKey().getClusterId());}}
> in ReplicationSink.
> In master-master replication scenarios, it would very useful if CopyTable
> would identify the source cluster (by tagging each Put/Delete with the source
> clusterId before applying it).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
