hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Duxbury (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-79) [hbase] When HBase needs to be migrated, it should display a message on stdout, not just in the logs
Date Wed, 06 Feb 2008 00:39:07 GMT

     [ https://issues.apache.org/jira/browse/HBASE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bryan Duxbury updated HBASE-79:
-------------------------------

    Fix Version/s: 0.2.0

> [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
>
>
> 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.


Mime
View raw message