hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-11726) Master should fail-safe if starting with a pre 0.96 layout
Date Fri, 29 Aug 2014 18:19:53 GMT

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

stack updated HBASE-11726:

       Resolution: Fixed
    Fix Version/s: 0.98.7
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Committed 0.98+. Thanks Esteban (And Srikanth for review)

> Master should fail-safe if starting with a pre 0.96 layout
> ----------------------------------------------------------
>                 Key: HBASE-11726
>                 URL: https://issues.apache.org/jira/browse/HBASE-11726
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.96.2, 0.99.0, 0.98.5, 2.0.0
>            Reporter: Esteban Gutierrez
>            Assignee: Esteban Gutierrez
>            Priority: Critical
>             Fix For: 0.99.0, 2.0.0, 0.98.7
>         Attachments: HBASE-11726.v0.diff, HBASE-11726.v1.diff, HBASE-11726.v2.diff
> We recently saw this: If user inadvertently starts the HBase Master after deploying new
HBase binaries (any version that supports namespaces), the HMaster will start the migration
to PBs the the {{hbase.version}} file per HBASE-5453 and that will write a new version file
PB-serialized but with the old version number. Further restarts of the master will fail because
the hbase version file has been migrated to PBs and there will be version mismatch. The right
approach should be to fail safe the master if we find an old {{hbase.version}} file in order
to force user to run upgrade tool.

This message was sent by Atlassian JIRA

View raw message