Ngone51 commented on pull request #32114: URL: https://github.com/apache/spark/pull/32114#issuecomment-825358789
> I tried this and the issue still exists. When we apply the sequence of events mentioned in #32114, the issue surfaces again. I see. I think I missed the code path of `scheduler.executorLost(executorId, lossReason)`. Thanks for the experiment. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
