[
https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352032#comment-15352032
]
Junping Du commented on YARN-5296:
----------------------------------
Thanks [~templedf] for review and comments! I think ContainerMetricsQuantiles
(include histogram) will be GCed when container is finished. Isn't it? The
memory leak happens here is because launched tasks never get chance to
shutdown, so it retain all container metrics and never get chance to release.
> NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl
> ---------------------------------------------------------------------------
>
> Key: YARN-5296
> URL: https://issues.apache.org/jira/browse/YARN-5296
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.8.0, 2.9.0
> Reporter: Karam Singh
> Assignee: Junping Du
> Attachments: YARN-5296.patch
>
>
> Ran tests in following manner,
> 1. Run GridMix of 768 sequestionally around 17 times to execute about 12.9K
> apps.
> 2. After 4-5hrs take Check NM Heap using Memory Analyser. It report around
> 96% Heap is being used my ContainerMetrics
> 3. Run 7 more GridMix run for have around 18.2apps ran in total. Again check
> NM heap using Memory Analyser again 96% heap is being used by
> ContainerMetrics.
> 4. Start one more grimdmix run, while run going on , NMs started going down
> with OOM, around running 18.7K+, On analysing NM heap using Memory analyser,
> OOM was caused by ContainerMetrics
--
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
