[
https://issues.apache.org/jira/browse/HBASE-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543136#comment-13543136
]
ramkrishna.s.vasudevan commented on HBASE-7369:
-----------------------------------------------
@Bryan Baugher
So HCM.locateRegion() would have thrown exception after this.
Its better to remove or while doing getConnection every time check if isClosed
== true and if so return a new connection.
bq.if an HTable throws an exception one should close it and retrieve a new one
Ya this should solve the problem if application takes care of it.
As Chunhui suggested we can move the code to close(). +1 from me. Also may be
we can improve the javadoc saying if your connection is closed then application
should handle it by creating a new one.
> HConnectionManager should remove aborted connections
> ----------------------------------------------------
>
> Key: HBASE-7369
> URL: https://issues.apache.org/jira/browse/HBASE-7369
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Affects Versions: 0.94.3
> Reporter: Bryan Baugher
> Priority: Minor
> Attachments: patch2.diff, patch3.diff, patch.diff
>
>
> When an HConnection is abort()'ed (i.e. if numerous services are lost) the
> connection becomes unusable. HConnectionManager cache of HConnections
> currently does not have any logic around removing aborted connections
> automatically. Currently it is up to the consumer to do so using
> HConnectionManager.deleteStaleConnection(HConnection).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
