You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/07/17 00:07:08 UTC

[jira] [Resolved] (HBASE-2623) Timeout on region open (to protect against case where a single borked region damages its table and others in the queue to be opened behind the bad one)

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

Andrew Purtell resolved HBASE-2623.
-----------------------------------

    Resolution: Cannot Reproduce

Reopen or file new issue if relevant for modern HBase versions

> Timeout on region open (to protect  against case where a single borked region damages its table and others in the queue to be opened behind the bad one)
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-2623
>                 URL: https://issues.apache.org/jira/browse/HBASE-2623
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: stack
>
> I witnessed a case last night where a region open got stuck -- it was an idx hbase region running on 0.20.5, seems like this combo doesn't work -- and it prevented our opening other regions behind it.  We never recovered.  Both the table that had the stuck region and all tables that had regions that were in the queue behind this stuck region were now borked.  There was no way out.
> Add a timeout on region open.  If a region open fails N times, put it aside.



--
This message was sent by Atlassian JIRA
(v6.2#6252)