[
https://issues.apache.org/jira/browse/SPARK-26688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey updated SPARK-26688:
---------------------------
Comment: was deleted
(was: Hi Imran,
thanks for you reply.
"Meanwhile devs start to apply this willy-nilly, as these configs tend to just
keep getting built up over time "
SLA could mitigate this problem. Every blacklisted node for a specific job
slows it down in a long run. Anyway, dev would have to report / communicate
with ops to resolve node issue.
"Ideally, blacklisting and speculation should be able to prevent that problem"
We are going to try out speculation but we are not there yet. )
> Provide configuration of initially blacklisted YARN nodes
> ---------------------------------------------------------
>
> Key: SPARK-26688
> URL: https://issues.apache.org/jira/browse/SPARK-26688
> Project: Spark
> Issue Type: Improvement
> Components: YARN
> Affects Versions: 3.0.0
> Reporter: Attila Zsolt Piros
> Assignee: Attila Zsolt Piros
> Priority: Major
> Fix For: 3.0.0
>
>
> Introducing new config for initially blacklisted YARN nodes.
> This came up in the apache spark user mailing list:
> [http://apache-spark-user-list.1001560.n3.nabble.com/Spark-on-Yarn-is-it-possible-to-manually-blacklist-nodes-before-running-spark-job-td34395.html]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
