hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3033) [Aggregator wireup] Implement NM starting the standalone ATS writer companion
Date Thu, 19 Mar 2015 14:55:40 GMT

    [ https://issues.apache.org/jira/browse/YARN-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369458#comment-14369458

Junping Du commented on YARN-3033:

Also, RM may not start a aggregatorCollection (with Rest server) just like what YARN-3034
currently did because all requests are coming from RM internally. Isn't it?

> [Aggregator wireup] Implement NM starting the standalone ATS writer companion
> -----------------------------------------------------------------------------
>                 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
>         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

View raw message