Details
Major Description
Each time a container's status is returned a log entry is produced in the NM from ContainerManagerImpl. The container status includes the diagnostics field for the container. If the diagnostics field contains an exception, it can appear as if the exception is logged repeatedly every second. The diagnostics message can also span many lines, which puts pressure on the logs and makes it harder to read.
For example:
2018-03-17 22:01:11,632 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl: Getting container-status for container_e01_1521323860653_0001_01_000005 2018-03-17 22:01:11,632 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl: Returning ContainerStatus: [ContainerId: container_e01_1521323860653_0001_01_000005, ExecutionType: GUARANTEED, State: RUNNING, Capability: <memory:1024, vCores:1>, Diagnostics: [2018-03-17 22:01:00.675]Exception from container-launch. Container id: container_e01_1521323860653_0001_01_000005 Exit code: -1 Exception message: <unknown> Shell ouput: <unknown> [2018-03-17 22:01:00.750]Diagnostic message from attempt : [2018-03-17 22:01:00.750]Container exited with a non-zero exit code -1. , ExitStatus: -1, IP: null, Host: null, ContainerSubState: SCHEDULED]