You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2015/01/29 18:14:35 UTC
[jira] [Resolved] (AMBARI-9377) hdfs superuser (usually user
'hdfs') should be in group dfs.cluster.administrators
[ https://issues.apache.org/jira/browse/AMBARI-9377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Onischuk resolved AMBARI-9377.
-------------------------------------
Resolution: Fixed
Committed to trunk
> hdfs superuser (usually user 'hdfs') should be in group dfs.cluster.administrators
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-9377
> URL: https://issues.apache.org/jira/browse/AMBARI-9377
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.0.0
>
>
> Noticed this on a HA cluster where the dfsadmin fetch image call failed with a
> 403 error.
> Fetch image call uses the value in dfs.cluster.administrators (hdfs-site.xml)
> to determine who the admin is. That is set to group hdfs. Other dfsadmin calls
> as user hdfs who belongs to group hadoop go through. But fetch image does not
> as hdfs does not belong to group hadoop. We should either add hdfs user to
> group hdfs or change this property to be set to group hadoop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)