Github user squito commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-143099031
I don't think I was totally clear about the suggestion for immediately
killing executors. I definitely did not mean that `BlacklistTracker` should be
making direct calls to yarn. But I do think it needs some way of "relaying"
that info on to appropriate allocators. It could "suggest" that the allocator
kill the executor (and request a new one), and the allocator is free to do what
it likes with that suggestion (eg., it could ignore completely). Meanwhile,
the tracker would blacklist the executor, and if eventually the allocator does
decide to remove it, then it can stop tracking that executor.
I think this is an important case even without dynamic allocation. If you
just request a static 5 executors, you're really want 5 good executors, not 5
executors with some mix of good and bad ones.
---
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]
