You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Ajay Jadhav (JIRA)" <ji...@apache.org> on 2017/02/14 18:28:42 UTC
[jira] [Created] (YARN-6188) Fix OOM issue with
decommissioningNodesWatcher in the case of clusters with large number of
nodes
Ajay Jadhav created YARN-6188:
---------------------------------
Summary: 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
Fix For: 2.9.0, 3.0.0-alpha1
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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org