[
https://issues.apache.org/jira/browse/HADOOP-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638831#action_12638831
]
dhruba borthakur commented on HADOOP-4386:
------------------------------------------
> async RPC calls. One should be able to invoke an RPC but not block waiting
> for the response, instead using a 'select'-style a
Isn't it enough to require that an asyncRPC is more like a sendMsg, in the
sense that it sends a message without expecting any response? Such a design
would satisfy the requirements of doing read/writes of user data. My assumption
is that such a RPC design would have lesser code complexity versus a design
that requires responses to be accumulated asynchronously and delivered to the
client application.
In this sense, asyncRPC is not completely non-blocking: it can experience
blocking while accessing sockets and files; but the "async" nature is that it
is not waiting for a application-level response from the remote server.
> RPC support for large data transfers.
> -------------------------------------
>
> Key: HADOOP-4386
> URL: https://issues.apache.org/jira/browse/HADOOP-4386
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs, ipc
> Reporter: Raghu Angadi
>
> Currently HDFS has a socket level protocol for serving HDFS data to clients.
> Clients do not use RPCs to read or write data. Fundamentally there is no
> reason why this data transfer can not use RPCs.
> This jira is place holder for any porting Datanode transfers to RPC. This
> topic has been discussed in varying detail many times, the latest being in
> the context of HADOOP-3856. There are quite a few issues to be resolved both
> at API level and at implementation level.
> We should probably copy some of the comments from HADOOP-3856 to here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
