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 "Daniel Templeton (JIRA)" <ji...@apache.org> on 2017/02/17 00:44:41 UTC
[jira] [Assigned] (YARN-6188) Fix OOM issue with
decommissioningNodesWatcher in the case of clusters with large number of
nodes
[ https://issues.apache.org/jira/browse/YARN-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Templeton reassigned YARN-6188:
--------------------------------------
Assignee: Ajay Jadhav
> Fix OOM issue with decommissioningNodesWatcher in the case of clusters with large number of nodes
> -------------------------------------------------------------------------------------------------
>
> Key: YARN-6188
> URL: https://issues.apache.org/jira/browse/YARN-6188
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.9.0
> Reporter: Ajay Jadhav
> Assignee: Ajay Jadhav
> Fix For: 2.9.0, 3.0.0-alpha1
>
> Attachments: YARN-6188.001.patch, YARN-6188.002.patch, YARN-6188.003.patch
>
>
> LogDecommissioningNodesStatus method in DecommissioningNodesWatcher uses StringBuilder to append status of all
> decommissioning nodes for logging purpose.
> In the case of large number of decommissioning nodes, this leads to OOM exception. The fix scopes StringBuilder so that in case of memory pressure, GC can kick in and free up the memory.
> This is supposed to fix a bug introduced in https://issues.apache.org/jira/browse/YARN-4676
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org