You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ken Weiner (JIRA)" <ji...@apache.org> on 2010/09/18 02:24:34 UTC
[jira] Created: (HBASE-3014) Change UnknownScannerException log
level to WARN
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:
{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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3014) Change UnknownScannerException log
level to WARN
Posted by "Ted Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913806#action_12913806 ]
Ted Yu commented on HBASE-3014:
-------------------------------
I attached a patch which includes region server name in exception messages.
I didn't change log level.
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-3014) Change UnknownScannerException log
level to WARN
Posted by "Ted Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-3014:
--------------------------
Attachment: hbase-3014.patch
Adding region server name to exception message
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3014) Change UnknownScannerException log
level to WARN
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913917#action_12913917 ]
stack commented on HBASE-3014:
------------------------------
@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.
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-3014) Change UnknownScannerException log
level to WARN
Posted by "Ken Weiner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Weiner updated HBASE-3014:
------------------------------
Priority: Trivial (was: Major)
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3014) Change UnknownScannerException log
level to WARN
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12911063#action_12911063 ]
stack commented on HBASE-3014:
------------------------------
>From mailing list:
{code}
I agree it needs some clarification, since that stuff evolved in
disparate ways. Historically UnknownScannerException has been fatal
and wasn't recovered from. Right now, the client will recover only if
the timeout hasn't expired (so you get this only when the region moves
or it took more than 60 seconds to call next). On top of that,
TableRecordReaderImpl will recover even if there's a timeout by
restarting a new scanner. The DoNotRetryIOException is only a way for
HBase to tell the HBase client that it shouldn't retry in the normal
retry code inside HConnectionManager, it's not a way to tell the
actual user that he shouldn't create a new scanner and retry.
Thus, the way I understand it, the fact that TRRI recovers from USE is
a design choice the same way someone using Scan in his code could
decide to retry scanning with a new scanner upon getting that error. I
like the way it currently works because if USE comes out of the
ResultScanner, it means that it took more than 60 seconds to process
one next() invocation so something is wrong (but the user can ignore
it like TRRI does).
That said, the exception should be printed as a WARN in the region
server log and probably shouldn't care printing a stack trace.
J-D
{code}
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-3014) Change UnknownScannerException log
level to WARN
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-3014:
-------------------------
Comment: was deleted
(was: From mailing list:
{code}
I agree it needs some clarification, since that stuff evolved in
disparate ways. Historically UnknownScannerException has been fatal
and wasn't recovered from. Right now, the client will recover only if
the timeout hasn't expired (so you get this only when the region moves
or it took more than 60 seconds to call next). On top of that,
TableRecordReaderImpl will recover even if there's a timeout by
restarting a new scanner. The DoNotRetryIOException is only a way for
HBase to tell the HBase client that it shouldn't retry in the normal
retry code inside HConnectionManager, it's not a way to tell the
actual user that he shouldn't create a new scanner and retry.
Thus, the way I understand it, the fact that TRRI recovers from USE is
a design choice the same way someone using Scan in his code could
decide to retry scanning with a new scanner upon getting that error. I
like the way it currently works because if USE comes out of the
ResultScanner, it means that it took more than 60 seconds to process
one next() invocation so something is wrong (but the user can ignore
it like TRRI does).
That said, the exception should be printed as a WARN in the region
server log and probably shouldn't care printing a stack trace.
J-D
{code}
)
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.