Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/17088
One meta question here: why aren't we getting a SlaveLost message in this
case? I'm asking since there's already code in #14931 to un-register shuffle
service files when we get a SlaveLost message, and that seems like a more
bulletproof way of handling the case where an entire slave goes down.
---
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]
