[
https://issues.apache.org/jira/browse/HBASE-8348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735700#comment-13735700
]
rajeshbabu commented on HBASE-8348:
-----------------------------------
bq. if a table is in ENABLIGN state then we may skip assignments during master
startup.
Sorry. Before migrating we will stop full cluster. During clean cluster startup
this problem wont happen.
bq. I think it is okay if we doc that the table which are disabled in 0.94.x,
might get enabled on migration. And, users could disable them once the
migration is done.
To do this, user need to note disabled tables before startup and then again
need to disable after migration. I feel its not good. Lets see what others will
tell on this.
> 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
>
>
> 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
