hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vrushali C (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-6888) Refactor AppLevelTimelineCollector such that RM does not have aggregator threads created
Date Thu, 27 Jul 2017 06:44:01 GMT

     [ https://issues.apache.org/jira/browse/YARN-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vrushali C updated YARN-6888:
-----------------------------
    Attachment: YARN-6888-YARN-5355.0001.patch


Attaching v001. 

Created subclass AppLevelTimelineCollectorWithAgg that handles the thread related agg stuff.
Creating this class in the NM and keeping the earlier AppLevelTimelineCollector class in RM.


> Refactor AppLevelTimelineCollector such that RM does not have aggregator threads created
> ----------------------------------------------------------------------------------------
>
>                 Key: YARN-6888
>                 URL: https://issues.apache.org/jira/browse/YARN-6888
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Vrushali C
>            Assignee: Vrushali C
>         Attachments: YARN-6888-YARN-5355.0001.patch
>
>
> Currently both RM and NM use the same AppLevelTimelineCollector class. The NM requires
aggregator threads per application so that it can perform in memory aggregation for application
metrics but the RM does not need this. Since they share the code, RM has a bunch of "TimelineCollector
Aggregation" threads created (one per running app).  
> Filing jira to refactor AppLevelTimelineCollector such that RM does not have aggregator
threads created. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message