[jira] [Resolved] (SPARK-3557) Yarn client config prioritization is backwards

["Thomas Graves (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Graves resolved SPARK-3557.
----------------------------------
    Resolution: Duplicate

> Yarn client config prioritization is backwards
> ----------------------------------------------
>
>                 Key: SPARK-3557
>                 URL: https://issues.apache.org/jira/browse/SPARK-3557
>             Project: Spark
>          Issue Type: Bug
>          Components: YARN
>    Affects Versions: 1.1.0
>            Reporter: Andrew Or
>
> In YarnClientSchedulerBackend, we have:
> {code}
> if (System.getenv(envVar) != null) {
>   arrayBuf += (optionName, System.getenv(envVar))
> } else if (sc.getConf.contains(sysProp)) {
>   arrayBuf += (optionName, sc.getConf.get(sysProp))
> }
> {code}
> Elsewhere in Spark we try to honor Spark configs over environment variables. This was introduced as a fix for the Yarn app name (SPARK-1631), but this also changed the behavior for other configs. Perhaps we should special case this particular config and correct the prioritization order of the other configs.



--
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