[ https://issues.apache.org/jira/browse/HBASE-11726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Esteban Gutierrez updated HBASE-11726: -------------------------------------- Attachment: HBASE-11726.v0.diff > 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 > Reporter: Esteban Gutierrez > Assignee: Esteban Gutierrez > Priority: Critical > Attachments: HBASE-11726.v0.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 (v6.2#6252)