[
https://issues.apache.org/jira/browse/SPARK-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487934#comment-14487934
]
Marcelo Vanzin commented on SPARK-6229:
---------------------------------------
Hi Jeff,
Those kinds of differences are exactly why I think all this channel setup code
should be handled by config options instead of having client code register
bootstraps and other things explicitly. I went with the latter approach to keep
the changes smaller (and even then they're still pretty intrusive). Aaron
doesn't seem to be a fan of that (config-based) approach, though.
For the SSL case, I haven't really looked at your code nor am I familiar with
how to use SSL in netty. Do you have to set it up as soon as the server starts
listening? (In which case you'd need some new `createServer()` method for SSL.)
Or can it be set up after the connection happens? (In which case, the
TransportServerBootstrap interface I added should suffice - just register the
handler when "doBootstrap()" is called.)
> Support SASL encryption in network/common module
> ------------------------------------------------
>
> Key: SPARK-6229
> URL: https://issues.apache.org/jira/browse/SPARK-6229
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Reporter: Marcelo Vanzin
>
> After SASL support has been added to network/common, supporting encryption
> should be rather simple. Encryption is supported for DIGEST-MD5 and GSSAPI.
> Since the latter requires a valid kerberos login to work (and so doesn't
> really work with executors), encryption would require the use of DIGEST-MD5.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
