[
https://issues.apache.org/jira/browse/SPARK-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907952#comment-14907952
]
Chris Heller commented on SPARK-8734:
-------------------------------------
Responsibilities have sort of pulled me away from focusing on this. I did
managed to get the network code in my branch.
I was thinking about parameters, and considered a scheme such as:
spark.mesos.executor.docker.parameter.<parameter-name> = <parameter-value>
This follows from how you set environment variables on the executor. Would this
scheme be reasonable?
> Expose all Mesos DockerInfo options to Spark
> --------------------------------------------
>
> Key: SPARK-8734
> URL: https://issues.apache.org/jira/browse/SPARK-8734
> Project: Spark
> Issue Type: Improvement
> Components: Mesos
> Reporter: Chris Heller
> Priority: Minor
> Attachments: network.diff
>
>
> SPARK-2691 only exposed a few options from the DockerInfo message. It would
> be reasonable to expose them all, especially given one can now specify
> arbitrary parameters to docker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
