[
https://issues.apache.org/jira/browse/HADOOP-10389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996017#comment-13996017
]
Binglin Chang commented on HADOOP-10389:
----------------------------------------
bq. The rationale behind call id in general is that in some future version of
the Java RPC system, we may want to allow multiple calls to be "in flight" at
once
I guess I always thought this is already implemented, because client already
can make parallel calls, and there are multiple rpc handler threads in server
side already, doing this should be natural and easy, although I haven't test
about this. Are you sure about this? If so I can try to add this in java...
bq. From the library user's perspective, they are calling hdfsOpen, hdfsClose,
etc. etc.
So those method all need to initialize hrpc_proxy again(which need server
address, user and other configs), what I try to say is maybe proxy and call can
be separated, proxy can be shared, call on stack for each call. Maybe it's to
late to change that, just my two cents.
bq. You just can't de-allocate the proxy while it is in use.
So there should be a method for user to cancel an ongoing rpc(also need to make
sure after cancel complete, no more memory access to hrpc_proxy and call),
looks like hrpc_proxy_deactivate can't do this yet?
> Native RPCv9 client
> -------------------
>
> Key: HADOOP-10389
> URL: https://issues.apache.org/jira/browse/HADOOP-10389
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: HADOOP-10388
> Reporter: Binglin Chang
> Assignee: Colin Patrick McCabe
> Attachments: HADOOP-10388.001.patch, HADOOP-10389.002.patch,
> HADOOP-10389.004.patch, HADOOP-10389.005.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
