Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/15267
It looks like you should be able to remove it after the
context.reply(ExecutorKilled) return. The killExecutors should be called
before the loss reason and if there is a race there its just going to go to
yarn to get the reason, which goes back to the same issue but I assume that
will be rare. We shouldn't be asking for the loss reason more then once.
---
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
