hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3801) Backup Master blocked when the HMaster Node Fail.
Date Wed, 20 Apr 2011 18:43:05 GMT

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

stack commented on HBASE-3801:
------------------------------

That looks like 'normal' behavior.  This is the condition the backup HMaster has and then
on primary's failure, its watch on the primary is triggered and above wait wakes up.  Is it
not happening for you?  What do you see?   The primary goes down and secondary does not assume
its role?

> Backup Master blocked when the HMaster Node Fail.
> -------------------------------------------------
>
>                 Key: HBASE-3801
>                 URL: https://issues.apache.org/jira/browse/HBASE-3801
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.90.2
>         Environment: 1 HMaster
> 1 HMaster -backup
> 6 HResignServer
>            Reporter: Aaron Guo
>
> When the HMaster crash, the Backup HMaster blocked for waiting the ZK notify.
> The Backup HMaster's thread stack is :
> "master-hp1:60000" prio=10 tid=0x00000000484c6800 nid=0x4b56 waiting on condition [0x0000000040209000]
>    java.lang.Thread.State: TIMED_WAITING (sleeping)
>         at java.lang.Thread.sleep(Native Method)
>         at org.apache.hadoop.hbase.master.HMaster.stallIfBackupMaster(HMaster.java:251)
>         at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:279)
>    Locked ownable synchronizers:
>         - None

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message