[
https://issues.apache.org/jira/browse/HBASE-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983016#action_12983016
]
stack commented on HBASE-3446:
------------------------------
As you said up on IRC, we actually weren't doing this fixup in shutdown
handling previously. Its new facility in 0.90.0. In 0.89, the basescanner
would try and do this fix up everytime it ran so I suppose it'd fail and then
come along later and probably succeed.
So, we've just read .META. in shutdown handling and now we're processing it.
Part of processing it is this new check on daughters. IF the .META. goes down
after we just successfully scanned it and before we've finished walking the
result to check on daughters, then we run into this issue. Seems rare enough?
> ProcessServerShutdown fails if META moves, orphaning lots of regions
> --------------------------------------------------------------------
>
> Key: HBASE-3446
> URL: https://issues.apache.org/jira/browse/HBASE-3446
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.0
> Reporter: Todd Lipcon
> Priority: Blocker
>
> I ran a rolling restart on a 5 node cluster with lots of regions, and
> afterwards had LOTS of regions left orphaned. The issue appears to be that
> ProcessServerShutdown failed because the server hosting META was restarted
> around the same time as another server was being processed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
