Github user thomastechs commented on the issue:
https://github.com/apache/spark/pull/16743
One point, as discussed, statusChange gets called for task status change.
So, if we can identify the point where the job or that executor(Only one
executor for local mode, right) is failed, we can give a call back at that
point. If you could give some insights about it, that fix can be applied.
---
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
