Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/17955
I've been running some local tests of scheduler throughput to make sure
that this doesn't adversely affect performance in the processing of task
completion events (I discovered the perf. hotspot fixed in #18008 as part of
this testing).
I'm planning to run more comprehensive end-to-end tests on real clusters
(with injected failures) in the next couple of days.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
