Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/19046
I was told that the preemption issue was fixed in YARN (that's YARN-6210);
so I don't think there's a need for this code currently (just use a fixed YARN
if you want reliable preemption).
Wilfred is on vacation so I can ask him details, but:
> It turns out that the AM is releasing and then acquiring the reservations
again and again until it has enough to run all tasks that it needs.
That could be an issue (don't remember details of the Spark allocator
code), but at the same time it sounds like a different issue than this was
trying to fix.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
