hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nkeywal (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5075) regionserver crashed and failover
Date Mon, 27 Feb 2012 13:35:48 GMT

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

nkeywal commented on HBASE-5075:
--------------------------------

In the case that you want to manage (region server crash without any hardware issue, i.e.
a pure application bug), a possible solution as well is loop in the launch script. This typically
allows 20s failover (stop time + start time), and is even compatible with hotfailover. It's
faster and less error prone than monitoring pid. But for HBase it would be a new start mode.
It could make sense if we observe much more application bugs than hw issues (this solution
is quite common with C/C++ stuff as it's easy to crash a process with these languages...)
                
> regionserver crashed and failover
> ---------------------------------
>
>                 Key: HBASE-5075
>                 URL: https://issues.apache.org/jira/browse/HBASE-5075
>             Project: HBase
>          Issue Type: Improvement
>          Components: monitoring, regionserver, replication, zookeeper
>    Affects Versions: 0.92.1
>            Reporter: zhiyuan.dai
>             Fix For: 0.90.5
>
>         Attachments: Degion of Failure Detection.pdf, HBase-5075-shell.patch, HBase-5075-src.patch
>
>
> regionserver crashed,it is too long time to notify hmaster.when hmaster know regionserver's
shutdown,it is long time to fetch the hlog's lease.
> hbase is a online db, availability is very important.
> i have a idea to improve availability, monitor node to check regionserver's pid.if this
pid not exsits,i think the rs down,i will delete the znode,and force close the hlog file.
> so the period maybe 100ms.

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

        

Mime
View raw message