You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Wei-Chiu Chuang (JIRA)" <ji...@apache.org> on 2016/02/11 21:25:18 UTC

[jira] [Commented] (HADOOP-12795) KMS does not log detailed stack trace for unexpected errors.

    [ https://issues.apache.org/jira/browse/HADOOP-12795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143439#comment-15143439 ] 

Wei-Chiu Chuang commented on HADOOP-12795:
------------------------------------------

Hi [~cnauroth], I've recently encountered similar issue with KMS returning code 500, and it would be great to add this log. We ended up looking at kms-catalina.log and found indirect evidence to the root cause. Have you checked that log too?

As for the patch, the log you added seem to be used in test only, not in production.

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