[ https://issues.apache.org/jira/browse/HADOOP-13854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao Chen updated HADOOP-13854: ------------------------------- Attachment: HADOOP-13854.03.patch Thanks [~yzhangal] for the review. I chose to log a stacktrace under the same condition as {{doAudit}} because I was more interested in the unknown errors, but not the access control errors. {code} // we don't audit here because we did it already when checking access {code} But I think logging more here shouldn't hurt - KMS logs usually has too little information than too much. So patch 3 uses your idea. :) > KMS should log error details even if a request is malformed > ----------------------------------------------------------- > > Key: HADOOP-13854 > URL: https://issues.apache.org/jira/browse/HADOOP-13854 > Project: Hadoop Common > Issue Type: Sub-task > Components: kms > Affects Versions: 2.6.5 > Reporter: Xiao Chen > Assignee: Xiao Chen > Attachments: HADOOP-13854.01.patch, HADOOP-13854.02.patch, > HADOOP-13854.03.patch > > > It appears if a KMS HTTP request is malformed, it could rejected by tomcat > and a response is sent by > [KMSExceptionsProvider|https://github.com/apache/hadoop/blob/branch-3.0.0-alpha1/hadoop-common-project/hadoop-kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSExceptionsProvider.java#L99] > overriding Jersey's ExceptionMapper. > This behavior is okay, but in the logs we'll see an ERROR audit log, but > nothing in kms.log (or anywhere else). This makes trouble shooting pretty > painful, let's improve it. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org