Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-7363

ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.0
    • Fix Version/s: 3.1.0, 2.10.0, 3.0.1
    • Component/s: nodemanager
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      In case of Linux container executor, ContainerLocalizer run as a separated process. It doesn't access a valid log4j.properties when the application user is not in the "hadoop" group. The log4j.properties of node manager is in its classpath, but it isn't readable by users not in hadoop group due to the security concern. In that case, ContainerLocalizer doesn't have a valid log4j configuration, and normally no log output.

        Attachments

        1. YARN-7363.branch-2.001.patch
          13 kB
          Yufei Gu
        2. YARN-7363.005.patch
          13 kB
          Yufei Gu
        3. YARN-7363.004.patch
          13 kB
          Yufei Gu
        4. YARN-7363.003.patch
          13 kB
          Yufei Gu
        5. YARN-7363.002.patch
          9 kB
          Yufei Gu
        6. YARN-7363.001.patch
          7 kB
          Yufei Gu

          Issue Links

            Activity

              People

              • Assignee:
                yufeigu Yufei Gu
                Reporter:
                yufeigu Yufei Gu
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: