spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (JIRA)" <>
Subject [jira] [Commented] (SPARK-16630) Blacklist a node if executors won't launch on it.
Date Thu, 05 Apr 2018 18:07:00 GMT


Thomas Graves commented on SPARK-16630:

the problem is that spark.executor.instances (or dynamic allocation) doesn't necessarily represent
the # of nodes in the cluster, especially if you look at dynamic allocation.  Depending on
the size of your nodes you can have a lot more executors then nodes, thus it could easily
end up blacklisting the entire cluster.  I would rather look at the actual # of nodes in
the cluster.  Is that turning out to be hard?

> Blacklist a node if executors won't launch on it.
> -------------------------------------------------
>                 Key: SPARK-16630
>                 URL:
>             Project: Spark
>          Issue Type: Improvement
>          Components: YARN
>    Affects Versions: 1.6.2
>            Reporter: Thomas Graves
>            Priority: Major
> On YARN, its possible that a node is messed or misconfigured such that a container won't
launch on it.  For instance if the Spark external shuffle handler didn't get loaded on it
, maybe its just some other hardware issue or hadoop configuration issue. 
> It would be nice we could recognize this happening and stop trying to launch executors
on it since that could end up causing us to hit our max number of executor failures and then
kill the job.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message