[
https://issues.apache.org/jira/browse/YARN-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538239#comment-13538239
]
Lohit Vijayarenu commented on YARN-287:
---------------------------------------
While running some tests I noticed that NodeManager does not log correct
physical/virtual memory values and causes little confusion.
As shown below, even though Xmx is set to 6G log says 1.0gb physical memory
configured and 2.1 virtual memory configured.
{noformat}
12/12/21 05:55:07 INFO mapreduce.Job: Task Id :
attempt_1356068333956_0002_r_000039_0, Status : FAILED
Container [pid=49507,containerID=container_1356068333956_0002_01_001723] is
running beyond virtual memory limits. Current usage: 63.8mb of 1.0gb physical
memory used; 6.3gb of 2.1gb virtual memory used. Killing container.
Dump of the process-tree for container_1356068333956_0002_01_001723 :
|- PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS)
SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE
|- 49507 39941 49507 49507 (java) 197 11 6792540160 16330
/usr/java/default/bin/java -Djava.net.preferIPv4Stack=true
-Dhadoop.metrics.log.level=WARN -Xmx6048m
-Djava.io.tmpdir=/data/disk2/yarn/local/usercache/hadoop/appcache/application_1356068333956_0002/container_1356068333956_0002_01_001723/tmp
-Dlog4j.configuration=container-log4j.properties
-Dyarn.app.mapreduce.container.log.dir=/data/disk6/yarn/logs/application_1356068333956_0002/container_1356068333956_0002_01_001723
-Dyarn.app.mapreduce.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA
org.apache.hadoop.mapred.YarnChild X.X.X.X 49683
attempt_1356068333956_0002_r_000039_0 1723
{noformat}
> NodeManager logs incorrect physical/virtual memory values
> ---------------------------------------------------------
>
> Key: YARN-287
> URL: https://issues.apache.org/jira/browse/YARN-287
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.0.3-alpha
> Reporter: Lohit Vijayarenu
> Priority: Minor
>
> Node manager does not log correct configured physical memory or virtual
> memory while killing containers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
