You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Esteban Gutierrez (JIRA)" <ji...@apache.org> on 2014/08/12 21:52:13 UTC
[jira] [Created] (HBASE-11726) Master should fail-safe if starting
with a pre 0.96 layout
Esteban Gutierrez created HBASE-11726:
-----------------------------------------
Summary: 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.98.5, 0.96.2, 0.99.0, 2.0.0
Reporter: Esteban Gutierrez
Assignee: Esteban Gutierrez
Priority: Critical
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
(v6.2#6252)