You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/07/19 02:41:38 UTC
[jira] [Resolved] (HBASE-3390) Double-close makes for double-assign
of a region
[ https://issues.apache.org/jira/browse/HBASE-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-3390.
-----------------------------------
Resolution: Cannot Reproduce
Reopen or file new issue if relevant with modern HBase versions
> Double-close makes for double-assign of a region
> ------------------------------------------------
>
> Key: HBASE-3390
> URL: https://issues.apache.org/jira/browse/HBASE-3390
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Attachments: history_of_region_in_master.txt
>
>
> I see double-assign during a rolling restart test. Its happening when master joins existing cluster... half the RSs have reported in but its taking on splits anyways (I have it splitting and balancing continuously). A split comes in immediately followed by a balance. What I think is happening is that the split comes in and clears a CLOSING from RIT as part of its cleanup of parent region references. This is messing up the run of balancers' close somehow; we're getting node created and children changed zk events and this makes somehow for the double closed.
> I'm enabling zk logging and will try harder to hunt this one down.
> Not creating as BLOCKER on 0.90.0 because I think its ok to disable balancer while rolling restart is going on -- and the current rolling restart is a horror anyways doing its maximmal region moving.
--
This message was sent by Atlassian JIRA
(v6.2#6252)