[
https://issues.apache.org/jira/browse/HBASE-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934770#action_12934770
]
Todd Lipcon commented on HBASE-3263:
------------------------------------
And also thereafter lots of these:
java.lang.NullPointerException
at
org.apache.hadoop.hbase.ipc.HBaseClient$Connection.sendParam(HBaseClient.java:485)
at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:733)
at org.apache.hadoop.hbase.ipc.HBaseRPC$Invoker.invoke(HBaseRPC.java:257)
at $Proxy8.getRegionInfo(Unknown Source)
at
org.apache.hadoop.hbase.catalog.CatalogTracker.verifyRegionLocation(CatalogTracker.java:416)
at
org.apache.hadoop.hbase.catalog.CatalogTracker.getMetaServerConnection(CatalogTracker.java:270)
at
org.apache.hadoop.hbase.catalog.CatalogTracker.waitForMeta(CatalogTracker.java:322)
So somehow we borked a null into one of our maps, it seems
> Stack overflow in AssignmentManager
> -----------------------------------
>
> Key: HBASE-3263
> URL: https://issues.apache.org/jira/browse/HBASE-3263
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.90.0
> Reporter: Todd Lipcon
> Priority: Blocker
> Attachments: stackoverflow-log.txt
>
>
> My test cluster experienced a switch outage earlier this week which threw the
> master into a really bad state. In the catch clause of
> AssignmentManager.assign, we recurse, and if all of the region servers are
> inaccessible, we do so until we get a stack overflow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
