[
https://issues.apache.org/jira/browse/HBASE-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925070#action_12925070
]
stack commented on HBASE-3153:
------------------------------
Problem seems to be as follows:
1. Rebalance
2. Close region
3. Handling close we queue a ClosedRegionHandler
4. Before it gets to run, we time out (lots of churn at this time) and the
region is reassigned (forced OFFLINE) and assigned.
5. Close handler runs and steps on above assignment
I see this:
{code}
2010-10-26 16:57:01,247 WARN org.apache.hadoop.hbase.master.AssignmentManager:
Received OPENED for region de6e83eaefdc9114c47fe5db7acbab96 from server
sv2borg187,60020,1288111711842 but region was in the state
usertable,user823757811,1287548184383.de6e83eaefdc9114c47fe5db7acbab96.
state=OFFLINE, ts=1288112221223
and not in expected PENDING_OPEN or OPENING states
{code}
I'm adding debug to confirm this is whats happening.
> "Attempting open of X but it's already online on this server"
> -------------------------------------------------------------
>
> Key: HBASE-3153
> URL: https://issues.apache.org/jira/browse/HBASE-3153
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.90.0
>
>
> Rolling restart I get some regions stuck in RIT with this message on the RS
> where we ask them open:
> {code}
> Attempting open of
> usertable,user823757811,1287548184383.de6e83eaefdc9114c47fe5db7acbab96. but
> it's already online on this server
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
