You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2011/07/28 01:15:09 UTC

[jira] [Commented] (HBASE-3447) Split parents ending up deployed along with daughters

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

stack commented on HBASE-3447:
------------------------------

I think we should close this issue.  Todd suggests:

bq. But even if we fixed HBASE-3446, we'd have this same bug if the master had crashed in the middle of processing the shutdown, right?

This is now in place.  See AssignmentManager#joinCluster.  See how it calls processDeadServers.  This in turn calls the same code used when recovering shutdown servers over in ServerShutdownHandler.processDeadRegion.

Is the above enough to close out this issue?

> Split parents ending up deployed along with daughters
> -----------------------------------------------------
>
>                 Key: HBASE-3447
>                 URL: https://issues.apache.org/jira/browse/HBASE-3447
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.0
>            Reporter: Todd Lipcon
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.92.0
>
>         Attachments: unknown-region.log
>
>
> Testing rc3 got several regions in this state as reported by hbck:
> ERROR: Region UNKNOWN_REGION on haus02.sf.cloudera.com:57020, key=9f2822a04028c86813fe71264da5c167, not on HDFS or in META but deployed on haus02.sf.cloudera.com:57020
> (this without any injected failures or anything)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira