Github user sitalkedia commented on the issue:
https://github.com/apache/spark/pull/17088
>> Why is this a no-op when the shuffle service isn't enabled? It looks
like you mark the slave as lost in all cases?
@kayousterhout - You are right. It's kind of confusing that we are
triggering a SlaveLost even in case of executor lost.
I made changes so that this change is going to effect only when we see a
fetch failure and external shuffle service is enabled. Let me know what you
think about it.
---
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]
