[YARN-7363] ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor

• 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
• Hadoop Flags: Reviewed
• Assignee: Yufei Gu
• Reporter: Yufei Gu
• Created: 19/Oct/17 03:26
• Updated: 24/Jan/18 14:26
• Resolved: 27/Nov/17 22:35

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.

Issue Links

• duplicates: YARN-5422 ContainerLocalizer log should be logged in separate log file.
• relates to: YARN-7705 Create the container log directory with correct sticky bit in C code