[
https://issues.apache.org/jira/browse/YARN-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311575#comment-16311575
]
Jason Lowe commented on YARN-7678:
----------------------------------
I filed YARN-7700 to track the TestContainerSchedulerQueuing failure.
+1 for the branch-2 patch as well. Committing this.
> Ability to enable logging of container memory stats
> ---------------------------------------------------
>
> Key: YARN-7678
> URL: https://issues.apache.org/jira/browse/YARN-7678
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
> Affects Versions: 2.8.0, 3.0.0
> Reporter: Jim Brennan
> Assignee: Jim Brennan
> Attachments: YARN-7678-branch-2.001.patch, YARN-7678.001.patch
>
>
> YARN-3424 changed logging of memory stats from ContainersMonitorImpl to INFO
> to DEBUG.
> We have found these log messages to be useful information in Out-of-Memory
> situations - they provide detail that helps show the memory profile of the
> container over time, which can be helpful in determining root cause.
> Here's an example message from YARN-3424:
> {noformat}
> 2015-03-27 09:32:48,905 INFO
> org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl:
> Memory usage of ProcessTree 9215 for container-id
> container_1427462602546_0002_01_000008: 189.8 MB of 1 GB physical memory
> used; 2.6 GB of 2.1 GB virtual memory used
> {noformat}
> Propose to change this to use a separate logger for this message, so that we
> can enable debug logging for this without enabling all of the other debug
> logging for ContainersMonitorImpl.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
