Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/12775#issuecomment-217659983
I'm not 100% convinced that we should be calling scheduler.handleFailedTask
after any Error resulting from the attempt to get the TaskEndReason from the
serializedData; but in the particular case of NoClassDefFoundError it seems to
me that we should be handling this similarly to what we are already doing with
ClassNotFoundException.
---
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]
