[
https://issues.apache.org/jira/browse/HBASE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-79:
-----------------------
Attachment: 79.patch
Patch that outputs this when you try to start a master on a system that needs
migration:
{code}
durruti:~/Documents/checkouts/hbase/trunk stack$ ./bin/start-hbase.sh
starting master, logging to
/Users/stack/Documents/checkouts/hbase/trunk/bin/../logs/hbase-stack-master-durruti.desk.hq.powerset.com.out
WARNING! File system needs upgrade. Run the '${HBASE_HOME}/bin/hbase migrate'
script. Master shutting down...
{code}
> [hbase] When HBase needs to be migrated, it should display a message on
> stdout, not just in the logs
> ----------------------------------------------------------------------------------------------------
>
> Key: HBASE-79
> URL: https://issues.apache.org/jira/browse/HBASE-79
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: util
> Reporter: Bryan Duxbury
> Fix For: 0.2.0
>
> Attachments: 79.patch
>
>
> When you upgrade your HBase code version, there is occasionally the need to
> migrate the underlying data store to a new version. However, if you are
> unaware of this need, then you'll be very confused by what happens when you
> restart HBase. Using start-hbase.sh, you get messages indicating that the
> master and regionservers started as expected. However, in reality, it will
> have tried to start and failed due to a version mismatch. This information is
> displayed in the logs, but you won't know that until you go log diving.
> Instead, let's have the start-hbase.sh script do a check to see if the
> version number is wrong itself. That way, if it fails, it can write messages
> about startup failure to the console instead of to the logs. This will make
> new admins much happier.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
