[
https://issues.apache.org/jira/browse/MAPREDUCE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840000#action_12840000
]
Vinod K V commented on MAPREDUCE-1542:
--------------------------------------
Allen, configuration of commong components is bound to be like this because of
the fact that we have a common codebase/project which both MAPREDUCE and HDFS
use. The configuration of the common components like Http servers, RPC
servers/clients will not have mapred/hdfs specific naming conventions. For
e.g., I don't see {{ipc.server.listen.queue.size}} or
{{ipc.client.connect.max.retries}} being split into mapred and hdfs specific
configuration items despite the fact that JT and NN need different values. I
think {{hadoop.cluster.administrators}} also falls under the same category.
> Deprecate mapred.permissions.supergroup in favor of
> hadoop.cluster.administrators
> ---------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1542
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1542
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: security
> Reporter: Vinod K V
> Fix For: 0.22.0
>
>
> HADOOP-6568 added the configuration {{hadoop.cluster.administrators}} through
> which admins can configure who the superusers/supergroups for the cluster
> are. MAPREDUCE itself already has {{mapred.permissions.supergroup}} (which is
> just a single group). As agreed upon at HADOOP-6568, this should be
> deprecated in favor of {{hadoop.cluster.administrators}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
