hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13854) KMS should log error details even if a request is malformed
Date Thu, 01 Dec 2016 23:10:58 GMT

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

Xiao Chen commented on HADOOP-13854:
------------------------------------

One example entry in the audit log is this intermittently:
{noformat}
2016-11-30 12:24:02,484 ERROR[user=impala] Method:'POST' Exception:'No content to map to Object
due to end of input'
{noformat}

The exception message is hardly helpful.

> 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: Improvement
>          Components: kms
>    Affects Versions: 2.6.5
>            Reporter: Xiao Chen
>            Assignee: Xiao Chen
>
> 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.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