[
https://issues.apache.org/jira/browse/HADOOP-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-2668:
--------------------------
Attachment: migration.patch
This patch is imcomplete. Adds migrate to ./bin/hbase. Adds doc. about
necessary migration to 'getting started' under javadoc. I started in adding to
the migration script extra info-level logging talking users through the process
so they have a better sense of whats happening but didn't finish the job
because need to study more what this script is up to (How about adding
description of migration steps to the class comment -- we can fill it out as we
add new steps).
The script doesn't have usage/help (-h/--help do nought). If I supply them, it
goes ahead and starts up the migration regardless. Do you think it should do
this? Should it not first emit flashing neon warnings about how this script
rewrites hbase.rootdir and of how it might make sense making a backup first,
etc. (Perhaps point at the MR CopyFiles or ./bin/hadoop distcp).
One idea would be that this script first checks to see if any migratory actions
are required; if so, user needs to rerun the migration script with an option
that says actually go ahead and rearrange hbase.rootdir.
> [hbase] Documentation and improved logging so fact that hbase now requires
> migration comes as less of a surprise
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-2668
> URL: https://issues.apache.org/jira/browse/HADOOP-2668
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 0.16.0
>
> Attachments: migrate.patch, migration.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.
