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