ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aravindan Vijayan (JIRA)" <j...@apache.org>
Subject [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
Date Tue, 15 Aug 2017 19:09:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-21729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aravindan Vijayan updated AMBARI-21729:
---------------------------------------
    Priority: Blocker  (was: Major)

> 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
>            Priority: Blocker
>             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)

Mime
View raw message