You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (Updated) (JIRA)" <ji...@apache.org> on 2011/11/01 17:23:32 UTC
[jira] [Updated] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-4713:
-------------------------
Comment: was deleted
(was: @Lars A patch?)
> Raise debug level to warn on ExecutionException in HConnectionManager$HConnectionImplementation
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-4713
> URL: https://issues.apache.org/jira/browse/HBASE-4713
> Project: HBase
> Issue Type: Improvement
> Reporter: Lucian George Iordache
>
> The ExecutionException is logged on debug level, and it should be logged on warn. I've met the problem in the next case:
> - hbase.rpc.timeout = 60000
> - lease time on region server = 240000
> - started a scan that takes more than 60 seconds on the region server ==> SocketTimeoutException logged on debug
> Having the log level on info, the exception was not observable on the client side and it took me a while to figure out what was hapenning.
> See also:
> - https://issues.apache.org/jira/browse/HBASE-3154
> - http://mail-archives.apache.org/mod_mbox/hbase-user/201110.mbox/%3CCANH3+J0athaCjK-ahu-A=hRZoOSjyh6s_mTpZM3_qQpfrcsGCg@mail.gmail.com%3E
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira