[
https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543511#comment-15543511
]
Xiao Chen commented on HADOOP-13669:
------------------------------------
Thanks for working on this [~sacharya]. I know this is still in the works, but
propose to only log the exception stack trace in debug, to prevent spamming the
server logs and unnecessary performance impact.
One way to do that is to log a higher level message without the stack trace,
and then log a DEBUG with stacktrace. But since we can already see the error
from client side, maybe just DEBUG logging the message + stack trace is fine.
Also ping [~asuresh] for his input.
> 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: [email protected]
For additional commands, e-mail: [email protected]
