hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Weiner (JIRA)" <j...@apache.org>
Subject [jira] Created: (HBASE-3014) Change UnknownScannerException log level to WARN
Date Sat, 18 Sep 2010 00:24:34 GMT
Change UnknownScannerException log level to WARN

                 Key: HBASE-3014
                 URL: https://issues.apache.org/jira/browse/HBASE-3014
             Project: HBase
          Issue Type: Improvement
          Components: regionserver
    Affects Versions: 0.20.6
            Reporter: Ken Weiner

I see a lot of UnknownScannerException messages in the log at ERROR level when I'm running
a MapReduce job that scans an HBase table.  These messages are logged under normal conditions,
and according to [~jdcryans], should probably be logged at a less severe log level like WARN.

Example error message:
2010-09-16 09:20:52,398 ERROR org.apache.hadoop.hbase.regionserver.HRegionServer: 
org.apache.hadoop.hbase.UnknownScannerException: Name: -8711007779313115048
	at org.apache.hadoop.hbase.regionserver.HRegionServer.next(HRegionServer.java:1880)
	at sun.reflect.GeneratedMethodAccessor8.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)

Reference to the HBase users mailing list thread where this was originally discussed:

This is a simple, change, so I didn't include a formal patch.  If one is required, I will
gladly create and attach one.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message