hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9740) A corrupt HFile could cause endless attempts to assign the region without a chance of success
Date Wed, 22 Jan 2014 06:13:22 GMT

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

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/12624279/patch-9740_0.94.txt
  against trunk revision .
  ATTACHMENT ID: 12624279

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/8490//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: Aditya Kishore
>         Attachments: 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.1.5#6160)

Mime
View raw message