[
https://issues.apache.org/jira/browse/YARN-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116075#comment-16116075
]
Sunil G commented on YARN-6871:
-------------------------------
Just took a quick scan, some more thoughts:
# {{deSelects}} params are using variable names from {{AppInfo}} DAO objects
which is correct. But this patch is using {{appTimeouts}} instead of
{{timeouts}} from AppInfo class. I think these need to be in sync. If we are
planning the name change in AppInfo DAO object for {{timeouts}}, I think that
also is fine. Looping [~rohithsharma] for additional thoughts on same.
# Existing resource request skip check in AppInfo ctor could also be moved down
with new changes so its easier to be together.
> Add additional deSelects params in getAppReport
> -----------------------------------------------
>
> Key: YARN-6871
> URL: https://issues.apache.org/jira/browse/YARN-6871
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: resourcemanager, router
> Reporter: Giovanni Matteo Fumarola
> Assignee: Tanuj Nayak
> Attachments: YARN-6871.002.patch, YARN-6871.003.patch,
> YARN-6871.proto.patch
>
>
> This jira tracks the effort to add additional deSelect params to the
> GetAppReport to make it lighter and faster.
> With the current one we are facing a scalability issues.
> E.g. with ~500 applications running the AppReport can reach up to 300MB in
> size due to the {{ResourceRequest}} in the {{AppInfo}}.
> Yarn RM will return the new result faster and it will use less compute cycles
> to create the report and it will improve the YARN RM and Client's
> performances.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
