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

Hudson commented on HADOOP-11615:
---------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #7233 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/7233/])
HADOOP-11615. Update ServiceLevelAuth.md for YARN. Contributed by Brahma Reddy 
Battula. (aajisaka: rev dd9cd0797c265edfa7c3f18d2efce7c8f2801a6d)
* hadoop-common-project/hadoop-common/src/site/markdown/ServiceLevelAuth.md
* hadoop-common-project/hadoop-common/CHANGES.txt


> Update ServiceLevelAuth.md for YARN
> -----------------------------------
>
>                 Key: HADOOP-11615
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11615
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 3.0.0
>            Reporter: Akira AJISAKA
>            Assignee: Brahma Reddy Battula
>            Priority: Minor
>             Fix For: 2.7.0
>
>         Attachments: HADOOP-11615-001.patch, HADOOP-11615-002.patch, 
> HADOOP-11615.patch, ServiceLevelAuth.md
>
>
> JobTracker should be ResourceManager, and {{hadoop mradmin}} should be {{yarn 
> rmadmin}} in ServiceLevelAuth.md.
> {code}
> The service-level authorization configuration for the NameNode and JobTracker 
> can be changed without restarting either of the Hadoop master daemons. The 
> cluster administrator can change `$HADOOP_CONF_DIR/hadoop-policy.xml` on the 
> master nodes and instruct the NameNode and JobTracker to reload their 
> respective configurations via the `-refreshServiceAcl` switch to `dfsadmin` 
> and `mradmin` commands respectively.
> Refresh the service-level authorization configuration for the NameNode:
>        $ bin/hadoop dfsadmin -refreshServiceAcl
> Refresh the service-level authorization configuration for the JobTracker:
>        $ bin/hadoop mradmin -refreshServiceAcl
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to