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 2012/08/28 20:10:07 UTC
[jira] [Commented] (HBASE-6660) Meta assignment to a region server
caused continuous NPE loop during postOpenDeployTasks
[ https://issues.apache.org/jira/browse/HBASE-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443329#comment-13443329 ]
stack commented on HBASE-6660:
------------------------------
@Shrijeet Did you want to make this a blocker on 0.92.2? What you think of Enis's question?
> Meta assignment to a region server caused continuous NPE loop during postOpenDeployTasks
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-6660
> URL: https://issues.apache.org/jira/browse/HBASE-6660
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.2
> Environment: CentOS release 5.7
> Reporter: Shrijeet Paliwal
> Priority: Blocker
>
> Recently I upgraded three data centers to our own checkout of 0.92.2, last commit :
> {noformat}
> commit 5accb6a1be4776630126ac21d07adb652b74df95
> Author: Zhihong Yu <te...@apache.org>
> Date: Mon Aug 20 18:19:45 2012 +0000
> HBASE-6608 Fix for HBASE-6160, META entries from daughters can be deleted before parent entries, shouldn't compare HRegionInfo's (Enis)
> {noformat}
> Two upgrades went fine, upgrade to one data center failed. Failed in the sense that ROOT and META assignment took forever. Panic struck I restarted master and all region servers. I may have deleted zookeeper node /hbase/root-region-server as well, dont ask me why :-(
> After this I managed to get ROOT assigned. But META assignment got stuck again.
> The log is here : https://raw.github.com/gist/3455435/adebd118b47aa3d715201010aa09e5eb8930033c/npe_rs_0.92.2.log
> Notice how region server was stuck in a loop of NPE (grep processBatchCallback). There is one more NPE related to zookeeper constructor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira