hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7158) Allow CopyTable to identify the source cluster (for replication scenarios)
Date Wed, 19 Dec 2012 23:45:13 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536603#comment-13536603

Jean-Daniel Cryans commented on HBASE-7158:

Ok I see it in 0.94, I guess the first time I compiled it was in 0.94 then I did it in trunk
and it was fine. Sorry about that! committed the fix.
> 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
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.96.0, 0.94.4
>         Attachments: HBASE-7158-0.94-v1.patch
> 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

View raw message