[
https://issues.apache.org/jira/browse/HBASE-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064688#comment-13064688
]
stack commented on HBASE-4087:
------------------------------
@Srivas Yes, we should bury it under the API if possible; add an isGood method
to Connection Interface. When connection goes bad, it marks itself so and
recourse is to go get a new one (This may not be possible).
@Ted so we need to change our APIs so that they all can catch IOE? How then to
tell difference between retryable IOE and one that makes the connection go
'bad'? We have already the Retryable exception interface that we have some
forms of IOE implement.
Is it true that the code previous to hbase-3777 had this same issue?
> 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
