You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Jacek Lewandowski (JIRA)" <ji...@apache.org> on 2015/10/26 23:25:28 UTC
[jira] [Created] (SPARK-11326) Split networking in standalone mode
Jacek Lewandowski created SPARK-11326:
-----------------------------------------
Summary: Split networking in standalone mode
Key: SPARK-11326
URL: https://issues.apache.org/jira/browse/SPARK-11326
Project: Spark
Issue Type: Improvement
Components: Spark Core
Reporter: Jacek Lewandowski
Currently, in standalone mode, all components, for all network connections need to use the same secure token if they want to have any security ensured.
This ticket is intended to split the communication in standalone mode to make it more like in Yarn mode - application internal communication, scheduler internal communication and communication between the client and scheduler.
Such refactoring will allow for the scheduler (master, workers) to use a distinct secret, which will remain unknown for the users. Similarly, it will allow for better security in applications, because each application will be able to use a distinct secret as well.
By providing Kerberos based SASL authentication/encryption for connections between a client (Client or AppClient) and Spark Master, it will be possible to introduce authentication and automatic generation of digest tokens and safe sharing them among the application processes.
--
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