[
https://issues.apache.org/jira/browse/HBASE-8348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739879#comment-13739879
]
stack commented on HBASE-8348:
------------------------------
There will be a pre-upgrade step for user to run before they take the cluster
offline. In it we'll ask them to run the v1 detector and if any found, keep
compacting till all hfile v1s are gone.
There is also the issue of meta edits that Himanshu came across. Not sure how
we are going to ensure .META. has all edits on shutdown if it not a 'clean'
shutdown.
[[email protected]] What are you referring to when you say "... It could
have issues with cyclic replication, for example"? Thanks.
> 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
