GitHub user steveloughran opened a pull request:
https://github.com/apache/spark/pull/6033
SPARK-7508 JettyUtils-generated servlets to log & report all errors
Patch for SPARK-7508
This logs @ warn then generates a respnse which include the message body
and stack trace as text/plain, no-cache. The exit code is 500.
In practise (in some tests in SPARK-1537 to be precise), jetty is getting
in between this servlet and the web response the user sees âthe body of the
response is lost for any error response (500, even 404 and bad request). The
standard Jetty handlers must be getting in the way.
This patch doesn't address that, it ensures that
# if the jetty handlers were put to one side the users would see the errors
# at least the exceptions appear in the server-side logs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/steveloughran/spark
stevel/feature/SPARK-7508-JettyUtils
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/6033.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #6033
----
commit 69c8263af8691284007c089d82c7cf5331038a2a
Author: Steve Loughran <[email protected]>
Date: 2015-05-09T18:31:39Z
SPARK-7508 JettyUtils-generated servlets to log & report 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]
