You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Tsz Wo (Nicholas), SZE (Updated) (JIRA)" <ji...@apache.org> on 2012/02/27 19:50:46 UTC

[jira] [Updated] (HADOOP-7635) RetryInvocationHandler should release underlying resources on close

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

Tsz Wo (Nicholas), SZE updated HADOOP-7635:
-------------------------------------------

    Fix Version/s: 0.23.3

I have merged this to 0.23.
                
> RetryInvocationHandler should release underlying resources on close
> -------------------------------------------------------------------
>
>                 Key: HADOOP-7635
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7635
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 0.24.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>             Fix For: 0.24.0, 0.23.3
>
>         Attachments: hadoop-7635.0.txt, hadoop-7635.1.txt
>
>
> It is often the case that RPC invocation handlers (e.g. {{o.a.h.ipc.WritableRpcEngine.Invoker}}) are wrapped in a {{RetryInvocationHandler}} instance to handle RPC retry logic. Since {{RetryInvocationHandler}} doesn't have any resources of its own, and is incapable of releasing the resources of the wrapped {{InvocationHandler}}, users of {{RetryInvocationHandler}} must keep around a reference to the underlying {{InvocationHandler}} only for the purpose of closing. For an example of this, see {{o.a.h.hdfs.DFSClient}}, in particular the member variables {{namenode}} and {{rpcNamenode}}.

--
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