[
https://issues.apache.org/jira/browse/HADOOP-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15534133#comment-15534133
]
Suraj Acharya commented on HADOOP-13317:
----------------------------------------
So the reason i have put it in is because we usually want to run the debug
only for some period of time and during that time period we want to be able to
figure out what exactly is happening.
Also, the information is not technically coming from the client since many
usecases might be where the hadoop key shell or some other process is making
the call and we want to see if there is a bug in the KMS side or in the
incoming messages.
> Add logs to KMS server-side to improve supportability
> -----------------------------------------------------
>
> Key: HADOOP-13317
> URL: https://issues.apache.org/jira/browse/HADOOP-13317
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Reporter: Xiao Chen
> Assignee: Suraj Acharya
> Priority: Minor
> Labels: supportability
> Attachments: HADOOP-13317-1.patch, HADOOP-13317-2.patch,
> HADOOP-13317-3.patch, HADOOP-13317-3.patch, HADOOP-13317.patch
>
>
> [KMS.java|https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMS.java]
> is the main class that serves KMS http requests. There're currently no logs
> at all, making trouble shooting difficult.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
