hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7369) HConnectionManager should remove aborted connections
Date Fri, 04 Jan 2013 19:12:14 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544118#comment-13544118

Ted Yu commented on HBASE-7369:

The above test failures were due to environment issue.
I triggered another build:
> 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: 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

View raw message