[
https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181869#comment-14181869
]
Jian He commented on YARN-2314:
-------------------------------
Jason, thanks for your explanation.
bq. If the cache never fills then we never will call removeProxy by the very
design of the cache.
I was thinking the client could have a way to explicitly stopProxy and remove
the entry from the cache, rather than remove the entry only if it hits the
cache limit. But looks like this is by design. And yes, this is the existing
behavior.
> ContainerManagementProtocolProxy can create thousands of threads for a large
> cluster
> ------------------------------------------------------------------------------------
>
> Key: YARN-2314
> URL: https://issues.apache.org/jira/browse/YARN-2314
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client
> Affects Versions: 2.1.0-beta
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Critical
> Attachments: YARN-2314.patch, YARN-2314v2.patch,
> disable-cm-proxy-cache.patch, nmproxycachefix.prototype.patch,
> tez-yarn-2314.xlsx
>
>
> ContainerManagementProtocolProxy has a cache of NM proxies, and the size of
> this cache is configurable. However the cache can grow far beyond the
> configured size when running on a large cluster and blow AM address/container
> limits. More details in the first comment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
