You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lucian George Iordache (Created) (JIRA)" <ji...@apache.org> on 2011/11/01 10:18:33 UTC
[jira] [Created] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
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
[jira] [Commented] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ 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_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
[jira] [Commented] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "Ted Yu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142022#comment-13142022 ]
Ted Yu commented on HBASE-4713:
-------------------------------
@Lucian:
Your attachment is a diff file which is not recognized by HadoopQA.
Can you generate a patch ?
See http://wiki.apache.org/hadoop/Hbase/HowToContribute
Once you check out source code and make the above modification, you can use 'svn diff > 4713.patch' to obtain 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
> 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_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
[jira] [Commented] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141286#comment-13141286 ]
stack commented on HBASE-4713:
------------------------------
@Lucien 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
[jira] [Commented] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142119#comment-13142119 ]
Hadoop QA commented on HBASE-4713:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12501940/4713.patch
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 javadoc. The javadoc tool appears to have generated -165 warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to introduce 42 new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.master.TestDistributedLogSplitting
org.apache.hadoop.hbase.master.TestMasterFailover
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/138//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/138//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/138//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: 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_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
[jira] [Updated] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-4713:
-------------------------
Resolution: Fixed
Fix Version/s: 0.92.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thank you for the patch Lucian George Iordache. I applied trunk and 0.92 branch..
> 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_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
[jira] [Updated] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "Lucian George Iordache (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lucian George Iordache updated HBASE-4713:
------------------------------------------
Status: Patch Available (was: Open)
Try 4713.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
> Affects Versions: 0.90.4
> Reporter: Lucian George Iordache
> 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_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
[jira] [Commented] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141283#comment-13141283 ]
stack commented on HBASE-4713:
------------------------------
@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
[jira] [Commented] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "Lucian George Iordache (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141302#comment-13141302 ]
Lucian George Iordache commented on HBASE-4713:
-----------------------------------------------
Will be provided soon
> 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
[jira] [Updated] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "Lucian George Iordache (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lucian George Iordache updated HBASE-4713:
------------------------------------------
Affects Version/s: 0.90.4
Status: Patch Available (was: Open)
> 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_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
[jira] [Commented] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ 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_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
[jira] [Updated] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "Lucian George Iordache (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lucian George Iordache updated HBASE-4713:
------------------------------------------
Status: Open (was: Patch Available)
> 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_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
[jira] [Commented] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142323#comment-13142323 ]
Hudson commented on HBASE-4713:
-------------------------------
Integrated in HBase-0.92 #100 (See [https://builds.apache.org/job/HBase-0.92/100/])
HBASE-4713 Raise debug level to warn on ExecutionException in HConnectionManager
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/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_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
[jira] [Updated] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "Lucian George Iordache (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lucian George Iordache updated HBASE-4713:
------------------------------------------
Attachment: 4713.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
> Affects Versions: 0.90.4
> Reporter: Lucian George Iordache
> 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_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
[jira] [Updated] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (HBASE-4713) Raise debug level to warn on
ExecutionException in HConnectionManager$HConnectionImplementation
Posted by "Lucian George Iordache (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lucian George Iordache updated HBASE-4713:
------------------------------------------
Attachment: HBASE-4713-patch.txt
> 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
> 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_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