[
https://issues.apache.org/jira/browse/HBASE-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064461#comment-13064461
]
Ted Yu commented on HBASE-4087:
-------------------------------
Patch version 2 addresses Srivas' comment.
It is incomplete. I want to get confirmation that similar changes should be
made to the files I mentioned in my email to dev@
The undeclaredThrowable field of UndeclaredThrowableException is an
IOException, similar to the following:
{code}
java.io.IOException: Call to /192.168.2.107:60697 failed on local exception:
java.io.IOException: Connection reset by peer
{code}
A test for this JIRA has been added in HBASE-4052:
TestMasterRestartAfterDisablingTable. I used that test to obtain the above
information.
Without fix for this JIRA, TestMasterRestartAfterDisablingTable wouldn't pass.
> HConnectionManager should perform validation of connection it hands out
> -----------------------------------------------------------------------
>
> Key: HBASE-4087
> URL: https://issues.apache.org/jira/browse/HBASE-4087
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Priority: Critical
> Fix For: 0.92.0
>
> Attachments: 4087-v2.txt, 4087.txt
>
>
> Through HBASE-3777, HConnectionManager reuses the connection to HBase servers.
> One challenge, discovered in troubleshooting HBASE-4052, is how we invalidate
> connection(s) to server which gets restarted.
> There're at least two ways.
> 1. HConnectionManager utilizes background thread(s) to periodically perform
> validation of connections in HBASE_INSTANCES and remove stale connection(s).
> 2. Allow HBaseClient (including HBaseAdmin) to provide feedback to
> HConnectionManager.
> The solution can be a combination of both of the above.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
