Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/7786
> by default Yarn will preempt the container 15 seconds after the warning
That's a long time and you can run a lot of tasks in that time. Unless
Spark actively goes and gets rid of these executors to play nice, this change
would probably harm performance more than it helps. So maybe instead we should
focus on stopping the executors so that dynamic allocation can bring up new
ones elsewhere?
Otherwise the current state is probably better.
---
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]
