hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5882) Prcoess RIT on master restart can try assigning the region if the region is found on a dead server instead of waiting for Timeout Monitor
Date Sat, 19 May 2012 11:26:10 GMT

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

Hudson commented on HBASE-5882:
-------------------------------

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #11 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/11/])
    HBASE-5882 Prcoess RIT on master restart can try assigning the region if the region is
found on a dead server instead of waiting for Timeout Monitor (Ashutosh) (Revision 1340392)

     Result = FAILURE
ramkrishna : 
Files : 
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java

                
> Prcoess RIT on master restart can try assigning the region if the region is found on
a dead server instead of waiting for Timeout Monitor
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5882
>                 URL: https://issues.apache.org/jira/browse/HBASE-5882
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.6, 0.92.1, 0.94.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: Ashutosh Jindal
>             Fix For: 0.96.0, 0.94.1
>
>         Attachments: HBASE-5882_v5.patch, hbase_5882.patch, hbase_5882_V2.patch, hbase_5882_V3.patch,
hbase_5882_V4.patch
>
>
> Currently on  master restart if it tries to do processRIT, any region if found on dead
server tries to avoid the nwe assignment so that timeout monitor can take care.
> This case is more prominent if the node is found in RS_ZK_REGION_OPENING state. I think
we can handle this by triggering a new assignment with a new plan.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message