Github user devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/18357
@jiangxb1987 Thanks for looking at this.
Any one of the threads in Worker gets an exception which is unhandled then
the thread gets terminated and process(Worker) keeps running, and the Worker
doesn't perform the terminated thread functionality. One instance I mentioned
in the JIRA description, where dispatcher-event thread got the exception and
terminated, worker keeps running without performing the terminated thread
functionality. I think we should handle this at the process level for all the
threads, if any thread gets unhandled exception then the process(Worker) should
exit instead of performing partial functionality.
This PR code change would set the default UncaughtExceptionHandler as
SparkUncaughtExceptionHandler and for any unhandled exception in any thread of
the process, SparkUncaughtExceptionHandler handles the exception and exit the
process with the appropriate exit code.
---
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
