[
https://issues.apache.org/jira/browse/HBASE-17704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892873#comment-15892873
]
Gary Helmling commented on HBASE-17704:
---------------------------------------
Just to be clear, I'd also be in favor of changing the default for this config
to Integer.MAX_VALUE for 1.4.0 and 2.0.0. The current situation having
FAILED_OPEN be a terminal state requiring operator intervention is pretty bad
and seems unnecessary.
It could be that I'm missing something else that's necessary, but that seems
like an appropriate fix for this issue.
> Regions stuck in FAILED_OPEN when HDFS blocks are missing
> ---------------------------------------------------------
>
> Key: HBASE-17704
> URL: https://issues.apache.org/jira/browse/HBASE-17704
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 1.1.8
> Reporter: Mathias Herberts
>
> We recently experienced the loss of a whole rack (6 DNs + RS) in a 120 node
> cluster. This lead to the regions which were present on the 6 RS which became
> unavailable to be reassigned to live RSs. When attempting to open some of the
> reassigned regions, some RS encountered missing blocks and issued "No live
> nodes contain current block Block locations" putting the regions in state
> FAILED_OPEN.
> Once the disappeared DNs went back online, the regions were left in
> FAILED_OPEN, needing a restart of all the affected RSs to solve the problem.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
