[
https://issues.apache.org/jira/browse/SPARK-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979173#comment-13979173
]
Nishkam Ravi commented on SPARK-1576:
-------------------------------------
Bit of a race condition here it seems. Patrick made a few changes yesterday
around the same time as I did (in ClientBase.scala):
for ((k, v) <- sys.props.filterKeys(_.startsWith("spark"))) {
JAVA_OPTS += "-D" + k + "=" + "\\\"" + v + "\\\""
}
This would allow JAVA_OPTS to be passed on the command line to the
ApplicationMaster, and accomplishes the same things as creation of a new
command line flag --spark-java-opts.
> Passing of JAVA_OPTS to YARN on command line
> --------------------------------------------
>
> Key: SPARK-1576
> URL: https://issues.apache.org/jira/browse/SPARK-1576
> Project: Spark
> Issue Type: Improvement
> Affects Versions: 0.9.0, 1.0.0, 0.9.1
> Reporter: Nishkam Ravi
> Fix For: 0.9.0, 1.0.0, 0.9.1
>
> Attachments: SPARK-1576.patch
>
>
> JAVA_OPTS can be passed by using either env variables (i.e., SPARK_JAVA_OPTS)
> or as config vars (after Patrick's recent change). It would be good to allow
> the user to pass them on command line as well to restrict scope to single
> application invocation.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
