[
https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142016#comment-13142016
]
Hadoop QA commented on HBASE-4713:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12501928/HBASE-4713-patch.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/135//console
This message is automatically generated.
> 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
> Attachments: 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
