[
https://issues.apache.org/jira/browse/YARN-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S resolved YARN-3741.
-------------------------------------
Resolution: Won't Fix
In ATSv2 weekly call, discussed for cleaning up JIRA which are not going
implement. Hence, closing the JIRA as Won't Fix. Feel free to reopen if still
same design approach exists.
> consider nulling member maps/sets of TimelineEntity
> ---------------------------------------------------
>
> Key: YARN-3741
> URL: https://issues.apache.org/jira/browse/YARN-3741
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Sangjin Lee
> Assignee: Vrushali C
> Priority: Major
> Labels: YARN-5355
>
> Currently there are multiple collection members of TimelineEntity that are
> always instantiated, regardless of whether they are used or not: info,
> configs, metrics, events, isRelatedToEntities, and relatesToEntities.
> Since TimelineEntities will be created very often and in lots of cases many
> of these members will be empty, creating these empty collections is wasteful
> in terms of garbage collector pressure.
> It would be good to start out with null members, and instantiate these
> collections only if they are actually used. Of course, we need to make that
> contract very clear and refactor all client code to handle that scenario.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
