Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/15249
If I understood the change correctly, a node can get blacklisted for a
taskset if sufficient (even different) tasks fail on executers on it.
Which can potentially cause all nodes to be blacklisted.
Or do you think this is contrived scenario that can't occur in practice? I
don't have sufficient context for motivating usecases/scenarios for this
geature.
On Oct 6, 2016 3:54 PM, "Kay Ousterhout" <[email protected]> wrote:
> @mridulm <https://github.com/mridulm> re: job failures, can you elaborate
> on the job failure scenario you're concerned about?
>
> Jobs can only fail when some tasks are unschedulable, which can happen if
> a task is permanently blacklisted on all available nodes. This can only
> happen when the number of nodes is smaller than the maximum number of
> failures for a particular tax attempt, and also seems like it's very
> similar to existing behavior: currently, if a task is blacklisted (even
> though the blacklist is temporary) on all nodes, the job will be failed (
> https://github.com/apache/spark/blob/master/core/src/
> main/scala/org/apache/spark/scheduler/TaskSetManager.scala#L595).
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/15249#issuecomment-252110900>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/ABhJlJRsIFR8Ng_USz1B-TmOZ3cOY1tcks5qxXwXgaJpZM4KHLvv>
> .
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
