[ https://issues.apache.org/jira/browse/HBASE-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278052#comment-13278052 ]
Hadoop QA commented on HBASE-5926: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12527860/5926.v9.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 hadoop23. The patch compiles against the hadoop 0.23.x profile. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 33 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1912//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1912//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1912//console This message is automatically generated. > Delete the master znode after a master crash > -------------------------------------------- > > Key: HBASE-5926 > URL: https://issues.apache.org/jira/browse/HBASE-5926 > Project: HBase > Issue Type: Improvement > Components: master, scripts > Affects Versions: 0.96.0 > Reporter: nkeywal > Assignee: nkeywal > Priority: Minor > Fix For: 0.96.0 > > Attachments: 5926.v6.patch, 5926.v8.patch, 5926.v9.patch > > > This is the continuation of the work done in HBASE-5844. > But we can't apply exactly the same strategy: for the region server, there is > a znode per region server, while for the master & backup master there is a > single znode for both. > So if we apply the same strategy as for a regionserver, we may have this > scenario: > 1) Master starts > 2) Backup master starts > 3) Master dies > 4) ZK detects it > 5) Backup master receives the update from ZK > 6) Backup master creates the new master node and become the main master > 7) Previous master script continues > 8) Previous master script deletes the master node in ZK > 9) => issue: we deleted the node just created by the new master > This should not happen often (usually the znode will be deleted soon enough), > but it can happen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira