[
https://issues.apache.org/jira/browse/YARN-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884376#comment-16884376
]
Daniel Templeton edited comment on YARN-6046 at 7/18/19 4:26 PM:
-----------------------------------------------------------------
LGTM +1 . I'll commit it when I get a dev environment again (unless some
generous soul wants to do it for me).
was (Author: templedf):
LGTM +1 . I'll commit it when I get a dev environment again (unless some
generous sole wants to do it for me).
> Documentation correction in YarnApplicationSecurity
> ---------------------------------------------------
>
> Key: YARN-6046
> URL: https://issues.apache.org/jira/browse/YARN-6046
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bibin A Chundatt
> Assignee: Yousef Abu-Salah
> Priority: Trivial
> Labels: newbie
> Attachments: YARN-6046.001.patch, yarn-6046.002.patch
>
>
> Few documentation correction required in
> hadoop-yarn/hadoop-yarn-site/YarnApplicationSecurity.html
> {code}
> 1. Suring AM startup, log in to Kerberos.
> {code}
> {code}
> Don’t. Rely on the lifespan of the
> {code}
> {code}
> renewed automatically; the AM pushes out
> {code}
> {code}
> In an insecure cluster, the application will run as the identity of the
> account of the node manager, typically something such as yarn or mapred. By
> default, the application will access HDFS as that user, with a different home
> directory, and with a different user identified in audit logs and on file
> system owner attributes.
> {code}
> Need to reframe sentence.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
