[ 
https://issues.apache.org/jira/browse/HBASE-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277190#comment-13277190
 ] 

Zhihong Yu commented on HBASE-5926:
-----------------------------------

{code}
+    "Usage: Master [opts] start|stop|cleanZNode\n" +
{code}
Please add document for cleanZNode command.
{code}
+   * delete the znode master if its content is same to the parameter
{code}
'znode master' -> 'master znode', 'same to' -> 'same as'
{code}
+    } catch (KeeperException ignore) {
+    } catch (IOException ignore) {
+    }
{code}
I would expect some logging for above cases.

                
> 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
>
>
> 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

        

Reply via email to