You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/11/16 21:11:58 UTC

[jira] [Resolved] (HBASE-5075) regionserver crashed and failover

     [ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-5075.
--------------------------
    Resolution: Won't Fix

The summary and description describe an issue we still have. The patch though is for something we have now in more modern hbase, the restart of a RS.

Resolving.

> 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.90.5
>            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 was sent by Atlassian JIRA
(v6.3.4#6332)