Github user lirui-intel commented on the pull request:

    https://github.com/apache/spark/pull/12775#issuecomment-218654108
  
    Thanks @markhamstra for the explanations. I think currently the thread just 
dies and we log the uncaught error. I can add a catch for NoClassDefFoundError 
and handle it the same way as ClassNotFoundException. But even with that, I 
think it's still better to inform the scheduler in finally to make sure the 
failed task is handled. Let me know what you think.


---
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]

Reply via email to