[jira] [Commented] (HADOOP-13903) KMS does not provide any useful debug information

["Steve Loughran (JIRA)" <ji...@apache.org>]

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

Steve Loughran commented on HADOOP-13903:
-----------------------------------------

I like extra logs, especially those for debugging security issues, so this is welcome.

# we normally just use {{LOG.debug()}}, over trace
# now we are moving to SL4J as classes get updated, you can move off the {{LOG.trace("User: [" + ugi.getShortUserName() + "] ")}} code and the {{.isTraceEnabled()}} guard, and just go: {{LOG.debug("User [{}]", ugi.getShortUserName)}}. No string concat will take place unless debug is enabled, so cost is minimal (one string object instantiation is all).

> 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
>         Attachments: 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org