Sangjin Lee commented on YARN-2928:

And sorry for going back on the name. :)

I realized that the term "aggregating" is now quite overloaded. When we said 
aggregation, we tried to stick with the definition of "adding up metrics to the 
next parent". In that sense, I'm not sure the timeline aggregator would be the 
best name, as it would not do that type of aggregation. "Aggregation" up to the 
app level would be done by the AM, and the flow run level aggregation is done 
by the backing storage.

How about "Timeline writer"?

> Application Timeline Server (ATS) next gen: phase 1
> ---------------------------------------------------
>                 Key: YARN-2928
>                 URL: https://issues.apache.org/jira/browse/YARN-2928
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Vinod Kumar Vavilapalli
>            Priority: Critical
>         Attachments: ATSv2.rev1.pdf, ATSv2.rev2.pdf
> We have the application timeline server implemented in yarn per YARN-1530 and 
> YARN-321. Although it is a great feature, we have recognized several critical 
> issues and features that need to be addressed.
> This JIRA proposes the design and implementation changes to address those. 
> This is phase 1 of this effort.

This message was sent by Atlassian JIRA

Reply via email to