[
https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142418#comment-13142418
]
Hudson commented on HBASE-4713:
-------------------------------
Integrated in HBase-TRUNK #2401 (See
[https://builds.apache.org/job/HBase-TRUNK/2401/])
HBASE-4713 Raise debug level to warn on ExecutionException in
HConnectionManager
stack :
Files :
* /hbase/trunk/CHANGES.txt
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
> 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
> Affects Versions: 0.90.4
> Reporter: Lucian George Iordache
> Fix For: 0.92.0
>
> Attachments: 4713.patch, HBASE-4713-patch.txt
>
>
> 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_qqpfrcs...@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
