[
https://issues.apache.org/jira/browse/HBASE-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983022#action_12983022
]
stack commented on HBASE-3447:
------------------------------
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?
You mean, the fixup needs to be run when master joins a cluster too? That
seems reasonable, a rare case, but yeah, somthing we should plug.
> 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
> Priority: Blocker
> 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.
-
You can reply to this email to add a comment to the issue online.
