You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2016/07/15 04:59:20 UTC
[jira] [Created] (HBASE-16234) Expect and handle nulls when
assigning replicas
Harsh J created HBASE-16234:
-------------------------------
Summary: Expect and handle nulls when assigning replicas
Key: HBASE-16234
URL: https://issues.apache.org/jira/browse/HBASE-16234
Project: HBase
Issue Type: Bug
Components: Region Assignment
Affects Versions: 1.2.0
Reporter: Harsh J
Observed this on a cluster:
{code}
FATAL org.apache.hadoop.hbase.master.HMaster: Unhandled exception. Starting shutdown.
java.lang.NullPointerException
at org.apache.hadoop.hbase.master.AssignmentManager.replicaRegionsNotRecordedInMeta(AssignmentManager.java:2799)
at org.apache.hadoop.hbase.master.AssignmentManager.assignAllUserRegions(AssignmentManager.java:2778)
at org.apache.hadoop.hbase.master.AssignmentManager.processDeadServersAndRegionsInTransition(AssignmentManager.java:638)
at org.apache.hadoop.hbase.master.AssignmentManager.joinCluster(AssignmentManager.java:485)
at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:723)
at org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:169)
at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1481)
at java.lang.Thread.run(Thread.java:745)
{code}
It looks like {{FSTableDescriptors#get(…)}} can be expected to return null in some cases, but {{AssignmentManager.replicaRegionsNotRecordedInMeta(…)}} does not currently have any handling for such a possibility.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)