Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18760
I'm not super sure this feature will be very useful with queues.
With queues, critical listeners (e.g. dynamic allocation) are very unlikely
to miss events. UI listeners are unlikely to miss events. That leaves the event
log, which can miss events more often in a large application, but how big of an
issue is that?
Also I don't understand why all the complicated code is needed. Why isn't
hold mode just calling `queue.put` (blocking) instead of `queue.offer`
(non-blocking)?
Long story short, I'd be sort of ok if the code was a lot simpler. But the
way it is, it sounds like too much complication for something that I don't
really expect to be that big of a problem anymore.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
