[
https://issues.apache.org/jira/browse/HBASE-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547258#comment-13547258
]
Ted Yu commented on HBASE-7369:
-------------------------------
I ran the following tests for 0.94 branch and they passed:
{code}
368 mt -Dtest=TestHCM
369 mt -Dtest=TestAdmin
371 mt -Dtest=TestMultiRowResource,TestTableMapReduce
{code}
Integrated to 0.94 branch
> 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
> Assignee: Bryan Baugher
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: 7369-0.94.txt, 7369-v5.txt,
> HBASE-7369_HCM-remove-aborted-cnxs-2.txt,
> HBASE-7369_HCM-remove-aborted-cnxs-3.txt,
> HBASE-7369_HCM-remove-aborted-cnxs-4.txt,
> HBASE-7369_HCM-remove-aborted-cnxs.txt, 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
