[
https://issues.apache.org/jira/browse/HBASE-9740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940273#comment-13940273
]
Hadoop QA commented on HBASE-9740:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12635500/HBase-9740_0.94_v4.patch
against trunk revision .
ATTACHMENT ID: 12635500
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9042//console
This message is automatically generated.
> A corrupt HFile could cause endless attempts to assign the region without a
> chance of success
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-9740
> URL: https://issues.apache.org/jira/browse/HBASE-9740
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.16
> Reporter: Aditya Kishore
> Assignee: Ping
> Fix For: 0.94.19
>
> Attachments: HBase-9740_0.94_v4.patch, HBase-9749_0.94_v2.patch,
> HBase-9749_0.94_v3.patch, patch-9740_0.94.txt
>
>
> As described in HBASE-9737, a corrupt HFile in a region could lead to an
> assignment storm in the cluster since the Master will keep trying to assign
> the region to each region server one after another and obviously none will
> succeed.
> The region server, upon detecting such a scenario should mark the region as
> "RS_ZK_REGION_FAILED_ERROR" (or something to the effect) in the Zookeeper
> which should indicate the Master to stop assigning the region until the error
> has been resolved (via an HBase shell command, probably "assign"?)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
