[
https://issues.apache.org/jira/browse/HADOOP-13903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815782#comment-15815782
]
Arun Suresh edited comment on HADOOP-13903 at 1/10/17 6:34 PM:
---------------------------------------------------------------
+1 for the latest patch. Will commit this to trunk tomorrow if no objections
from anyone else.
[~tmgstev], will you be posting a branch-2 patch (since this is targeted for
2.9.0 as well) ?
was (Author: asuresh):
+1 for the latest patch. Will commit this to trunk tomorrow if no objects from
anyone else.
[~tmgstev], will you be posting a branch-2 patch (since this is targeted for
2.9.0 as well) ?
> KMS does not provide any useful debug information
> -------------------------------------------------
>
> Key: HADOOP-13903
> URL: https://issues.apache.org/jira/browse/HADOOP-13903
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
> Affects Versions: 2.9.0, 3.0.0-alpha2
> Reporter: Tristan Stevens
> Assignee: Tristan Stevens
> Priority: Minor
> Attachments: HADOOP-13903-2.patch, HADOOP-13903-3.patch,
> HADOOP-13903-5-branch2.7.patch, HADOOP-13903-5.patch, HADOOP-13903-6.patch,
> HADOOP-13903-6.patch, HADOOP-13903-7.patch, HADOOP-13903-branch2.7-6.patch,
> HADOOP-13903-branch2.7-7.patch, HADOOP-13903.patch
>
>
> At the moment there is no debug or trace level logs generated for KMS
> authorisation decisions. In order for users to understand what is going on in
> given scenarios this would be invaluable.
> Code should endeavour to keep as much work off the sunny-day-code-path as
> much as possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
