Github user yogeshg commented on the issue:
https://github.com/apache/spark/pull/22912
In an offline discussion with @MrBago , we noted that there's at most as
many (non-cancelled) `timerTasks` on the `timer` as there are slots. So, one
thread for managing logging is probably fine, in fact if anything, we should
also think about how we can just use the main thread. Also, this means that the
`timer.purge()` call in the finally block is also `O(n + log c) \in
O(constant)` where `n` is the total number of tasks and `c` is the number of
cancelled tasks.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
