[ https://issues.apache.org/jira/browse/YARN-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohith Sharma K S resolved YARN-3033. ------------------------------------- Resolution: Won't Fix Closing the JIRA as Won't Fix. Feel free to reopen if still same design approach exists. > [Collector wireup] Implement NM starting the standalone timeline collector > daemon > --------------------------------------------------------------------------------- > > Key: YARN-3033 > URL: https://issues.apache.org/jira/browse/YARN-3033 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Sangjin Lee > Assignee: Li Lu > Priority: Major > Labels: YARN-5355 > Attachments: MappingandlaunchingApplevelTimelineaggregators.pdf > > > Per design in YARN-2928, implement node managers starting the ATS writer > companion. In YARN-2928, we already have an auxiliary service based solution. > Per discussion below, the bulk of that approach has actually been done as > part of YARN-3030. In this ticket we can work on the remaining tasks, for > example: > # any needed change for configuration, esp. running it inside the NM (e.g. > the number of servlet threads) > # set up a start script that starts the per-node aggregator as a standalone > daemon > # for the standalone mode, implement a service that receives requests to set > up and tear down the app-level data -- 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