Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-21729

Owner of yarn.include stays to be root:root where as dfs.include gets changed to the correct one upon restart services

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 2.5.2
    • 2.5.2
    • ambari-admin
    • None

    Description

      • 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

      Attachments

        1. AMBARI-21729_2.patch
          341 kB
          Dmytro Sen
        2. AMBARI-21729.patch
          9 kB
          Dmytro Sen

        Issue Links

          Activity

            People

              dsen Dmytro Sen
              dbalasundaran Dhanya Balasundaran
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: