[
https://issues.apache.org/jira/browse/SPARK-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335234#comment-14335234
]
Reynold Xin commented on SPARK-5124:
------------------------------------
[~vanzin] I agree - it would be better to have a receive function that just
takes a message and sender information. But that is what the current design
provides, isn't it? There is an explicit sender. Are you suggesting getting rid
of the partial function?
For synchronization. I keep going back and forth on this. For generality, it is
better for the RPC interface to not enforce any synchronization, and let the
endpoints synchronize themselves. However, we do reduce the potential of
application errors.
cc [~adav]
> Standardize internal RPC interface
> ----------------------------------
>
> Key: SPARK-5124
> URL: https://issues.apache.org/jira/browse/SPARK-5124
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Reporter: Reynold Xin
> Assignee: Shixiong Zhu
> Attachments: Pluggable RPC - draft 1.pdf, Pluggable RPC - draft 2.pdf
>
>
> In Spark we use Akka as the RPC layer. It would be great if we can
> standardize the internal RPC interface to facilitate testing. This will also
> provide the foundation to try other RPC implementations in the future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
