You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "nkeywal (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/12 00:06:39 UTC

[jira] [Resolved] (HBASE-5053) HCM Tests leak connections

     [ https://issues.apache.org/jira/browse/HBASE-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nkeywal resolved HBASE-5053.
----------------------------

    Resolution: Fixed
    
> HCM Tests leak connections
> --------------------------
>
>                 Key: HBASE-5053
>                 URL: https://issues.apache.org/jira/browse/HBASE-5053
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.94.0
>            Reporter: nkeywal
>            Assignee: nkeywal
>            Priority: Minor
>             Fix For: 0.94.0
>
>         Attachments: 5053.patch, 5053.v2.patch, 5053.v2.patch
>
>
> There are simple leaks and one more complex.
> The complex one comes from the fact fact HConnectionManager.HConnectionImplementation keeps a *reference* to the configuration used for the creation. So if this configuration is updated later, the HConnectionKey created initially will differ from the current one. As a consequence, the close() will not find the connection anymore in the list, and the connection won't be deleted.
> I added a warning when a close does not find the connection in the list; but I wonder if we should not copy the HConnectionKey instead of keeping a reference.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira