[
https://issues.apache.org/jira/browse/HADOOP-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337091#comment-14337091
]
Akira AJISAKA commented on HADOOP-11615:
----------------------------------------
bq. ..I think since it is so big line
I don't think so. Could you retry?
I missed one more {{mradmin}}. Would you fix it?
{code}
| security.refresh.policy.protocol.acl | ACL for
RefreshAuthorizationPolicyProtocol, used by the dfsadmin and mradmin commands
to refresh the security policy in-effect. |
{code}
> Remove MRv1-specific terms from ServiceLevelAuth.md
> ---------------------------------------------------
>
> 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
> Attachments: HADOOP-11615.patch
>
>
> 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)
