[
https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15547877#comment-15547877
]
Xiao Chen commented on HADOOP-13669:
------------------------------------
I agree those errors usually indicate a problem. But my concern is that,
assuming we have 1 problematic key which throws exceptions, we may end up
seeing that key log a bunch of stacktraces, hence spamming the log and also
impacting server performance. Making it debug can give us more control (e.g.
choose to temporarily turn it on on 1 KMS instance etc.)
> 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]
