[
https://issues.apache.org/jira/browse/HBASE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-3014.
--------------------------
Resolution: Cannot Reproduce
Marking as 'can not repro'. I think this issue is actually fixed after doing a
survey. No where do we log this exception explicitly at the ERROR level (not
any more at least). It is all INFO-level that I can see.
> 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
> Priority: Trivial
> Attachments: hbase-3014.patch
>
>
> 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:
> {code}
> 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)
> {code}
> Reference to the HBase users mailing list thread where this was originally
> discussed:
> http://markmail.org/thread/ttzbi6c7et6mrq6o
> 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 was sent by Atlassian JIRA
(v6.2#6252)
