[
https://issues.apache.org/jira/browse/YARN-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933646#comment-15933646
]
Wangda Tan commented on YARN-6285:
----------------------------------
Thanks [~zhaoyunjiong] for sharing the experimental results. Now I can
understand why the YARN-6339 required and I will check it in once it is ready.
For your last comment:
bq. On the cluster we applied this patch and set
yarn.resourcemanager.max-limit-get-applications to 400
I'm actually not sure about which part improves performance since there're two
variables (patch of YARN-6339 and changes of #apps). It will be more helpful if
you can gets some benchmarks from config with only one variable.
> Add option to set max limit on ResourceManager for
> ApplicationClientProtocol.getApplications
> --------------------------------------------------------------------------------------------
>
> Key: YARN-6285
> URL: https://issues.apache.org/jira/browse/YARN-6285
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: yunjiong zhao
> Assignee: yunjiong zhao
> Attachments: YARN-6285.001.patch, YARN-6285.002.patch,
> YARN-6285.003.patch
>
>
> When users called ApplicationClientProtocol.getApplications, it will return
> lots of data, and generate lots of garbage on ResourceManager which caused
> long time GC.
> For example, on one of our RM, when called rest API " http://<rm http
> address:port>/ws/v1/cluster/apps" it can return 150MB data which have 944
> applications.
> getApplications have limit parameter, but some user might not set it, and
> then the limit will be Long.MAX_VALUE.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
