You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2015/10/08 05:04:26 UTC

[jira] [Created] (SPARK-10997) Netty-based RPC env should support a "client-only" mode.

Marcelo Vanzin created SPARK-10997:
--------------------------------------

             Summary: Netty-based RPC env should support a "client-only" mode.
                 Key: SPARK-10997
                 URL: https://issues.apache.org/jira/browse/SPARK-10997
             Project: Spark
          Issue Type: Improvement
          Components: Spark Core
    Affects Versions: 1.6.0
            Reporter: Marcelo Vanzin


The new netty RPC still behaves too much like akka; it requires both client (e.g. an executor) and server (e.g. the driver) to listen for incoming connections.

That is not necessary, since sockets are full-duplex and RPCs should be able to flow either way on any connection. Also, because the semantics of the netty-based RPC don't exactly match akka, you get weird issues like SPARK-10987.

Supporting a client-only mode also reduces the number of ports Spark apps need to use.



--
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