Github user kayousterhout commented on the issue: https://github.com/apache/spark/pull/12775 @mridulm My thought here was we might as well catch it, since the thread is about to die anyway. The alternative is that we don't catch it, the thread dies (so the error disappears / we never see it), and then the VM is in the same inconsistent state. At least the error message from catching it might provide a useful hint about what happened.
--- 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