HBase
  1. HBase
  2. HBASE-3014

Change UnknownScannerException log level to WARN

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Trivial Trivial
    • Resolution: Cannot Reproduce
    • Affects Version/s: 0.20.6
    • Fix Version/s: None
    • Component/s: regionserver
    • Labels:
      None

      Description

      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 Jean-Daniel Cryans, 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:
      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.

        Activity

        Hide
        Ted Yu added a comment -

        Adding region server name to exception message

        Show
        Ted Yu added a comment - Adding region server name to exception message
        Hide
        Ted Yu added a comment -

        I attached a patch which includes region server name in exception messages.
        I didn't change log level.

        Show
        Ted Yu added a comment - I attached a patch which includes region server name in exception messages. I didn't change log level.
        Hide
        stack added a comment -

        @Ted I took a look at your patch. It seems to address an issue other than what Ken describes. Do you want to open a new issue for your patch (Add a bit of justification for why you think server name is needed on the exception – is it not decodable otherwise? Maybe not?) Thanks Ted.

        Show
        stack added a comment - @Ted I took a look at your patch. It seems to address an issue other than what Ken describes. Do you want to open a new issue for your patch (Add a bit of justification for why you think server name is needed on the exception – is it not decodable otherwise? Maybe not?) Thanks Ted.
        Hide
        stack added a comment -

        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.

        Show
        stack added a comment - 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.

          People

          • Assignee:
            Unassigned
            Reporter:
            Ken Weiner
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development