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

rajeshbabu commented on HBASE-8348:
-----------------------------------

Himanshu,
bq. a) I think you should also remove the hbase.id znode as master has to 
rewrite it anyway. Also, talking to Matteo, also delete online-snapshot znode. 
That way, there will be only two znodes left: table, replication.
I will remove these. 

If we use replication znode backup tool, failures can happen in multiple places 
a) while taking backup b) deleting znodes c) while restoring right?
Need to handle all cases and user also need to aware of them while running 
again on failure?
But with replacement, just if we run the same command again we can continue 
from the place where its failed. Its simple to use also.

Lets see what others will say about this. If its ok to use backup tool, for me 
also no problem.
                
> 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.96.0
>
>         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