hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suraj Acharya (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13669) KMS Server should log exceptions before throwing
Date Mon, 03 Oct 2016 21:45:20 GMT

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

Suraj Acharya commented on HADOOP-13669:
----------------------------------------

I agree with the logic of it being a bit too much.
However, my thought process was that since most of these errors will be a fatal error (either
killing the operation in progress / killing the startup of the KMS) i thought it was worth
putting this as an error message.
But ill take whatever recommendation you'll give me on this one.

> KMS Server should log exceptions before throwing
> ------------------------------------------------
>
>                 Key: HADOOP-13669
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13669
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: kms
>            Reporter: Xiao Chen
>            Assignee: Suraj Acharya
>              Labels: supportability
>         Attachments: HADOOP-13369.patch
>
>
> In some recent investigation, it turns out when KMS throws an exception (into tomcat),
it's not logged anywhere and we can only see the exception message from client-side, but not
the stacktrace. Logging the stacktrance would help debugging.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message