Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/12775#issuecomment-218521768
@lirui-intel Sorry, I don't have anything specific at this time. In
general, catching Errors is a bad idea. In this particular case, we may be
able to handle NoClassDefFoundError well enough that we can effectively turn it
into the equivalent of a ClassNotFoundException. I haven't even looked yet to
figure out what we are doing with uncaught Throwables in this part of the code,
but what I am thinking is that we may need a handler for those that will at
least try to have the scheduler handle failed tasks and maybe also do some
other things on the way toward what is likely an attempted clean shutdown --
but you're correct that we can't really expect such things to succeed for all
Errors.
---
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]
