hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-7635) RetryInvocationHandler should release underlying resources on close
Date Wed, 14 Sep 2011 23:22:09 GMT

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

Aaron T. Myers updated HADOOP-7635:
-----------------------------------

    Status: Patch Available  (was: Open)

I should have also mentioned: I took the liberty of converting {{TestRPC}} to a Junit 4-style
test.

> RetryInvocationHandler should release underlying resources on close
> -------------------------------------------------------------------
>
>                 Key: HADOOP-7635
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7635
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.24.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>             Fix For: 0.24.0
>
>         Attachments: hadoop-7635.0.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message