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

Himanshu Vashishtha commented on HBASE-8348:
--------------------------------------------

For a waledit, the clusterId of the originator cluster is the identifier. In 
current code, Replicationsource decides whether an edit is to be shipped to a 
sink by comparing the sink's clusterId with waledits' clusterid (ship it if 
clusterid is different). 
In case we change it, replication of older edits (tagged with older clusterId) 
will be shipped back to the origin cluster again, as the clusterid will not 
match. Without HBase-7709, it will cause infinite loop. With proposed 7709 fix, 
they will be shipped back to the origin cluster once.
                
> Polish the migration to 0.96
> ----------------------------
>
>                 Key: HBASE-8348
>                 URL: https://issues.apache.org/jira/browse/HBASE-8348
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.95.0
>            Reporter: Jean-Daniel Cryans
>            Assignee: rajeshbabu
>            Priority: Critical
>             Fix For: 0.95.2
>
>         Attachments: HBASE-8348_trunk.patch, HBASE-8348_trunk_v2.patch, 
> HBASE-8348_trunk_v3.patch
>
>
> Currently, migration works but there's still a couple of rough edges:
>  - HBASE-8045 finished the .META. migration but didn't remove ROOT, so it's 
> still on the filesystem.
>  - Data in ZK needs to be removed manually. Either we fix up the data in ZK 
> or we delete it ourselves.
>  - TestMetaMigrationRemovingHTD has a testMetaUpdatedFlagInROOT method, but 
> ROOT is gone now.
> Elliott was also mentioning that we could have "hbase migrate" do the HFileV1 
> checks, clear ZK, remove ROOT, etc.

--
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

Reply via email to