hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-12795) KMS does not log detailed stack trace for unexpected errors.
Date Thu, 11 Feb 2016 20:18:18 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-12795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth updated HADOOP-12795:
-----------------------------------
    Attachment: HADOOP-12795.001.patch

It appears there was some consideration of logging stack traces at some point.  There is a
{{KMSExceptionsProvider#log}} method that would log the stack trace, but I can't find any
code that calls that method.  Maybe we just need to add a call to that method when there is
an internal server error.  (See attached patch.)

[~asuresh], could you please comment?  Thank you.

> KMS does not log detailed stack trace for unexpected errors.
> ------------------------------------------------------------
>
>                 Key: HADOOP-12795
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12795
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: kms
>            Reporter: Chris Nauroth
>         Attachments: HADOOP-12795.001.patch
>
>
> If the KMS server encounters an unexpected error resulting in an HTTP 500 response, it
does not log the stack trace.  This makes it difficult to troubleshoot.  The client side exception
cannot provide further details.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message