[jira] [Commented] (YARN-8045) Reduce log output from container status calls

["Eric Badger (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YARN-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893064#comment-16893064 ] 

Eric Badger commented on YARN-8045:
-----------------------------------

[~shanekumpf@gmail.com], [~ccondit], do you have any concerns with me porting this back all the way through branch-2? I see that you avoided breaking parsers that would ingest this log, but I'm not sure if it's acceptable to remove logging from older, more stable releases. 

cc [~Jim_Brennan]

> Reduce log output from container status calls
> ---------------------------------------------
>
>                 Key: YARN-8045
>                 URL: https://issues.apache.org/jira/browse/YARN-8045
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Shane Kumpf
>            Assignee: Craig Condit
>            Priority: Major
>             Fix For: 3.2.0
>
>         Attachments: YARN-8045.001.patch
>
>
> 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:
> {code}
> 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]
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org