Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/6033#issuecomment-100926303
Latest patch logs then rethrows; a jetty error handler created on jetty
server startup will catch this and convert it into a 500+ error page. The jetty
handler doesn't log anything, so you do need both for diagnostics at both ends.
There's no tests, it [is in the SPARK-1537 failure
simulation](https://github.com/steveloughran/spark/blob/stevel/feature/SPARK-1537-ATS/yarn/history/src/test/scala/org/apache/spark/deploy/history/yarn/failures/MockWebsiteFailure.scala)
---
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]
