You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Andrea Peruffo (JIRA)" <ji...@apache.org> on 2015/04/09 15:14:12 UTC
[jira] [Commented] (SPARK-6028) Provide an alternative RPC
implementation based on the network transport module
[ https://issues.apache.org/jira/browse/SPARK-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487329#comment-14487329 ]
Andrea Peruffo commented on SPARK-6028:
---------------------------------------
The main blocking problem in the implementation looks like:
org.apache.spark.deploy.client.AppClient
that needs to be heavily refactored in order to avoid the use of akka,
also an abstract remote naming convention will be made available outside the Akka one (maybe hidden in the RpcEnv?).
Also "object RpcEnv" is private and there will be no way of provide an alternative implementation of the protocol because rpcEnvNames are hard coded, in this case I will suggest the use of an assignable implicit argument instead of loading the class through Reflection.
> Provide an alternative RPC implementation based on the network transport module
> -------------------------------------------------------------------------------
>
> Key: SPARK-6028
> URL: https://issues.apache.org/jira/browse/SPARK-6028
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Reporter: Reynold Xin
>
> Network transport module implements a low level RPC interface. We can build a new RPC implementation on top of that to replace Akka's.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org