You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2017/08/15 15:35:02 UTC
[jira] [Updated] (AMBARI-21729) Owner of yarn.include stays to be
root:root where as dfs.include gets changed to the correct one upon restart
services
[ https://issues.apache.org/jira/browse/AMBARI-21729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmytro Sen updated AMBARI-21729:
--------------------------------
Attachment: AMBARI-21729.patch
> Owner of yarn.include stays to be root:root where as dfs.include gets changed to the correct one upon restart services
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-21729
> URL: https://issues.apache.org/jira/browse/AMBARI-21729
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
> Affects Versions: 2.5.2
> Reporter: Dhanya Balasundaran
> Assignee: Dmytro Sen
> Fix For: 2.5.2
>
> Attachments: AMBARI-21729.patch
>
>
> - After deployment, create dfs.include and yarn.include in /etc/hadoop/conf as root user itself. - Set manage.include.files to true for HDFS and YARN and update dfs.hosts and yarn.resourcemanager.nodes.include-path properties
> - Restart services
> - After services are restrated dfs.include gets the right owner (<serviceuser>:hadoop) where as yarn.include still has root:root
> - Noticed that owner of dfs.include is updated during Namenode restart but yarn.include is not updated after restart of all services that had stale configs
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)