[
https://issues.apache.org/jira/browse/SPARK-29070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Masiero Vanzin resolved SPARK-29070.
--------------------------------------------
Fix Version/s: 3.0.0
Assignee: Jeff Evans
Resolution: Fixed
> Make SparkLauncher log full spark-submit command line
> -----------------------------------------------------
>
> Key: SPARK-29070
> URL: https://issues.apache.org/jira/browse/SPARK-29070
> Project: Spark
> Issue Type: Improvement
> Components: Spark Submit
> Affects Versions: 2.4.5
> Reporter: Jeff Evans
> Assignee: Jeff Evans
> Priority: Minor
> Fix For: 3.0.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> {{org.apache.spark.launcher.SparkLauncher}} wraps a {{ProcessBuilder}}, and
> builds up a full command line to {{spark-submit}} using a builder pattern.
> When {{startApplication}} is finally called, a full command line is
> materialized out of all the options, then invoked via the {{ProcessBuilder}}.
> In scenarios where another application is submitting to Spark, it would be
> extremely useful from a support and debugging standpoint to be able to see
> the full {{spark-submit}} command that is actually used (so that the same
> submission can be tested standalone, arguments tweaked, etc.). Currently,
> the only way this gets captured is to {{stderr}} if the
> {{SPARK_PRINT_LAUNCH_COMMAND}} environment variable is set. This is
> cumbersome in the context of an application that is wrapping Spark and
> already using the APIs.
> I propose simply making {{SparkSubmit}} log the full command line it is about
> to launch, so that clients can see it directly in their log files, rather
> than having to capture and search through {{stderr}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
