[ https://issues.apache.org/jira/browse/YARN-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888147#comment-16888147 ]
Hudson commented on YARN-6046: ------------------------------ FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16953 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/16953/]) YARN-6046. Fixed documentation error in YarnApplicationSecurity. (eyang: rev 9838a47d44c31ac8557b4e8f67c1676c356ec9f7) * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/YarnApplicationSecurity.md > 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: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org