[
https://issues.apache.org/jira/browse/HBASE-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730667#action_12730667
]
Haijun Cao commented on HBASE-1634:
-----------------------------------
I am getting the same NPE after hbase crashed, after restart the hbase, the NPE
shows up from UI master.jsp.
Below is the log when hbase crashed, thought it might provide some context for
why NPE happens later.
Also, I understand it is not the old NPE in BaseScanner, but I apply the same
fix (basically replace getRegionInfo with getRegionInfoOrNull, it seem to work
(UI is up). But I have no idea if it will cause other problems somewhere
else....
2009-07-13 16:42:22,338 WARN org.apache.hadoop.hbase.master.BaseScanner: Scan
one META region: {server: 10.10.30.148:60
020, regionname: .META.,,1, startKey: <>}
org.apache.hadoop.hbase.UnknownScannerException:
org.apache.hadoop.hbase.UnknownScannerException: Name: -39524747077288
85071
at
org.apache.hadoop.hbase.regionserver.HRegionServer.next(HRegionServer.java:1884)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.next(HRegionServer.java:1870)
at sun.reflect.GeneratedMethodAccessor6.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:643)
at
org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:913)
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.master.BaseScanner.scanRegion(BaseScanner.java:191)
at
org.apache.hadoop.hbase.master.MetaScanner.scanOneMetaRegion(MetaScanner.java:73)
at
org.apache.hadoop.hbase.master.MetaScanner.maintenanceScan(MetaScanner.java:129)
at
org.apache.hadoop.hbase.master.BaseScanner.chore(BaseScanner.java:135)
at org.apache.hadoop.hbase.Chore.run(Chore.java:68)
2009-07-13 16:42:22,339 FATAL org.apache.hadoop.hbase.master.HMaster: Shutting
down HBase cluster: file system not avai
lable
java.io.IOException: File system is not available
at
org.apache.hadoop.hbase.util.FSUtils.checkFileSystemAvailable(FSUtils.java:123)
at
org.apache.hadoop.hbase.master.HMaster.checkFileSystem(HMaster.java:324)
at
org.apache.hadoop.hbase.master.MetaScanner.scanOneMetaRegion(MetaScanner.java:89)
at
org.apache.hadoop.hbase.master.MetaScanner.maintenanceScan(MetaScanner.java:129)
at
org.apache.hadoop.hbase.master.BaseScanner.chore(BaseScanner.java:135)
at org.apache.hadoop.hbase.Chore.run(Chore.java:68)
Caused by: java.io.IOException: Filesystem closed
at org.apache.hadoop.hdfs.DFSClient.checkOpen(DFSClient.java:197)
at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:585)
at
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:453)
at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:643)
at
org.apache.hadoop.hbase.util.FSUtils.checkFileSystemAvailable(FSUtils.java:112)
... 5 more
2009-07-13 16:42:22,339 INFO org.apache.hadoop.hbase.master.BaseScanner: All 1
.META. region(s) scanned
2009-07-13 16:42:22,339 INFO org.apache.hadoop.hbase.master.BaseScanner: All 1
.META. region(s) scanned
> UI and shell list throw NPE
> ---------------------------
>
> Key: HBASE-1634
> URL: https://issues.apache.org/jira/browse/HBASE-1634
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.20.0
>
>
> I have a .META. from bryan duxbury that has a row with only historian data.
> List does whole row, not just info, so if only historian entries, a row is
> returned. We then try and get a regioninfo from this row and NPE.
> As to why this happens, jd suggests that since we moved to async historian
> updates, row may have been deleted already. Confirm.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
