You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Bibin Chundatt (Jira)" <ji...@apache.org> on 2021/03/05 05:26:00 UTC
[jira] [Comment Edited] (YARN-10649) Fix
RMNodeImpl.updateExistContainers leak
[ https://issues.apache.org/jira/browse/YARN-10649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295251#comment-17295251 ]
Bibin Chundatt edited comment on YARN-10649 at 3/5/21, 5:25 AM:
----------------------------------------------------------------
Thank you [~max2049] for contribution.. Committed to trunk and branch3.3
was (Author: bibinchundatt):
Thank you [~max2049] for contribution.. Committed to trunk
> Fix RMNodeImpl.updateExistContainers leak
> -----------------------------------------
>
> Key: YARN-10649
> URL: https://issues.apache.org/jira/browse/YARN-10649
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 3.3.0
> Reporter: Max Xie
> Assignee: Max Xie
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.1
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> YARN-5168 the patch added RMNodeImpl.updatedExistContainers, but it didn't remove completed containers.
> These objects (ContainerStatusPBImpl & ContainerIdPBImpl ) stay in RMNodeImpl.updatedExistContainers forever.
> Because of this leak, ResourceManager in our production environment encountered OOM issue. We found 13 million ContainerStatusPBImpl objects in the heap dump file of ResourceManager.
> The patch has been applied in our production env and so far it works well.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org