You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2018/04/30 20:41:00 UTC

[jira] [Resolved] (SPARK-24003) Add support to provide spark.executor.extraJavaOptions in terms of App Id and/or Executor Id's

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

Marcelo Vanzin resolved SPARK-24003.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.4.0

Issue resolved by pull request 21088
[https://github.com/apache/spark/pull/21088]

> Add support to provide spark.executor.extraJavaOptions in terms of App Id and/or Executor Id's
> ----------------------------------------------------------------------------------------------
>
>                 Key: SPARK-24003
>                 URL: https://issues.apache.org/jira/browse/SPARK-24003
>             Project: Spark
>          Issue Type: Improvement
>          Components: Mesos, Spark Core, YARN
>    Affects Versions: 2.3.0
>            Reporter: Devaraj K
>            Assignee: Devaraj K
>            Priority: Major
>             Fix For: 2.4.0
>
>
> Users may want to enable gc logging or heap dump for the executors, but there is a chance of overwriting it by other executors since the paths cannot be expressed dynamically. This improvement would enable to express the spark.executor.extraJavaOptions paths in terms of App Id and Executor Id's to avoid the overwriting by other executors.
> There was a discussion about this in SPARK-3767, but it never fixed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org