[
https://issues.apache.org/jira/browse/HBASE-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874782#action_12874782
]
Jeff Whiting commented on HBASE-2585:
-------------------------------------
The meta region was online and mostly working. I say mostly because we were
having a weird problem where for a few regions (most worked just fine) the
master would get a region open message but the meta table was never updated
with the assignment information. Because it was a test cluster we just
formated the namenode and started over.
> NPE in HRegionServer when attempting to assignSplitDaughter
> -----------------------------------------------------------
>
> Key: HBASE-2585
> URL: https://issues.apache.org/jira/browse/HBASE-2585
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.20.4
> Environment: Linux dsmaster 2.6.32-21-server #32-Ubuntu SMP Fri Apr
> 16 09:17:34 UTC 2010 x86_64 GNU/Linux
> HBase 0.20.4
> Reporter: Jeff Whiting
>
> While inserting a large number of rows into a HBase table (approx 100M) we
> got this error many times (usually do to multiple attempts) on one of our
> region servers:
> 2010-05-19 16:51:30,745 WARN
> org.apache.hadoop.hbase.regionserver.HRegionServer: Attempt=1
> java.io.IOException: java.io.IOException: java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.ServerManager.assignSplitDaughter(ServerManager.java:535)
> at
> org.apache.hadoop.hbase.master.ServerManager.processSplitRegion(ServerManager.java:512)
> at
> org.apache.hadoop.hbase.master.ServerManager.processMsgs(ServerManager.java:463)
> at
> org.apache.hadoop.hbase.master.ServerManager.processRegionServerAllsWell(ServerManager.java:414)
> at
> org.apache.hadoop.hbase.master.ServerManager.regionServerReport(ServerManager.java:323)
> at
> org.apache.hadoop.hbase.master.HMaster.regionServerReport(HMaster.java:724)
> at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:657)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:915)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at
> org.apache.hadoop.hbase.RemoteExceptionHandler.decodeRemoteException(RemoteExceptionHandler.java:94)
> at
> org.apache.hadoop.hbase.RemoteExceptionHandler.checkThrowable(RemoteExceptionHandler.java:48)
> at
> org.apache.hadoop.hbase.RemoteExceptionHandler.checkIOException(RemoteExceptionHandler.java:66)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:577)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
