[ https://issues.apache.org/jira/browse/HBASE-11726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115800#comment-14115800 ]
Hudson commented on HBASE-11726: -------------------------------- FAILURE: Integrated in HBase-1.0 #139 (See [https://builds.apache.org/job/HBase-1.0/139/]) HBASE-11726 Master should fail-safe if starting with a pre 0.96 layout (Esteban Guiterrez) (stack: rev 8362e6222262b97596c91657c7354326e5ce8620) * hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java > 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 (v6.2#6252)