[
https://issues.apache.org/jira/browse/HADOOP-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560752#action_12560752 ]
stack commented on HADOOP-2668:
-------------------------------
It didn't occur to me that migration was the way to fix the missing version file. I also figured we should just auto-migrate this one case of a missing version file (If in future, version file goes missing, I'd think it the job of hbsfck recreating it, rather than migration?).
But I'm fine w/ forcing users to run the migration. It needs to be better documented and added to the bin/hbase script with verb 'migrate' I'd say.
I tried to run the migration but it wants to connect to a HMaster. That ain't going to work (Cluster won't start because no version file... can't migrate because cluster ain't up...).
> [hbase] After 2643, cluster won't start if FS was created by an older hbase version
> -----------------------------------------------------------------------------------
>
> Key: HADOOP-2668
> URL:
https://issues.apache.org/jira/browse/HADOOP-2668> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: stack
> Priority: Blocker
> Fix For: 0.16.0
>
> Attachments: migrate.patch
>
>
> Hbase now checks for a version file. If none, it reports a version mismatch. There will be no version file if the hbase was made by a version older than r613469
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
