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

Hudson commented on HBASE-8750:
-------------------------------

Integrated in hbase-0.95 #260 (See 
[https://builds.apache.org/job/hbase-0.95/260/])
    HBASE-8750 MetaServerShutdownHandler stucks if .META. assignment fails in 
previous attempt (Revision 1495747)

     Result = FAILURE
jxiang : 
Files : 
* 
/hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/catalog/CatalogTracker.java
* 
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/MetaServerShutdownHandler.java

                
> MetaServerShutdownHandler stucks if .META. assignment fails in previous 
> attempt
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-8750
>                 URL: https://issues.apache.org/jira/browse/HBASE-8750
>             Project: HBase
>          Issue Type: Bug
>          Components: MTTR
>    Affects Versions: 0.95.1
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
>             Fix For: 0.98.0, 0.95.2
>
>         Attachments: HBASE-8750-v0.patch, HBASE-8750-v1.patch
>
>
> While running log replay on a one node setup, I killed meta regionserver. The 
> MetaSSH tries to assign the meta table, but it failed as there was no other 
> regionservers to assign to. But the meta server znode was already updated to 
> null. When the assignment fails, the metaSSH is retried. But from the next 
> iteration, it will not try to assign the meta region, but keeps on waiting 
> for meta region. This keeps on going even after regionserver is brought up 
> again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to