[
https://issues.apache.org/jira/browse/YARN-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15805333#comment-15805333
]
Junping Du commented on YARN-6062:
----------------------------------
bq. HADOOP-13362 leads to heap memory OOM right. But here RES memory is leaking.
In my understanding, RES include a process' heap memory. No?
We have met so many NM OOM cases in different 2.7.x clusters, all of them are
end up with NM metrics leak that HADOOP-13362 resolved. As mentioned by
[~sjlee0], I would suggest to provide dump analysis with some tools (like MAT,
etc.) rather than guessing from limited information. It should be clear soon
afterwards.
> nodemanager memory leak
> -----------------------
>
> Key: YARN-6062
> URL: https://issues.apache.org/jira/browse/YARN-6062
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.7.1
> Reporter: gehaijiang
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 8986 data 20 0 21.3g 19g 7376 S 5.5 20.7 2458:09 java
> 38432 data 20 0 9.8g 7.9g 6300 S 95.5 8.4 35273:23 java
> 6653 data 20 0 4558m 3.4g 10m S 9.2 3.6 6640:37 java
> $ jps
> 6653 NodeManager
> Nodemanager memory has been up，Reach 10G。
> nodemanager yarn-env.sh configure (2G)
> YARN_NODEMANAGER_OPTS=" -Xms2048m -Xmn768m
> -Xloggc:${YARN_LOG_DIR}/nodemanager.gc.log -XX:+PrintGCDateStamps
> -XX:+PrintGCDetails -XX:+PrintGCTimeStamps"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
