You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith Sharma K S (Jira)" <ji...@apache.org> on 2019/08/30 05:47:00 UTC
[jira] [Resolved] (YARN-3817) [Aggregation] Flow and User level
aggregation on Application States table
[ https://issues.apache.org/jira/browse/YARN-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohith Sharma K S resolved YARN-3817.
-------------------------------------
Resolution: Won't Fix
As part of ATSv2 JIRA clean up as discussed in weekly call, closing the JIRA as Won't Fix. Feel free to reopen if still same design approach exists.
> [Aggregation] Flow and User level aggregation on Application States table
> -------------------------------------------------------------------------
>
> Key: YARN-3817
> URL: https://issues.apache.org/jira/browse/YARN-3817
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Junping Du
> Assignee: Li Lu
> Priority: Major
> Labels: YARN-5355
> Attachments: Detail Design for Flow and User Level Aggregation.pdf, YARN-3817-poc-v1-rebase.patch, YARN-3817-poc-v1.patch
>
>
> We need time-based flow/user level aggregation to present flow/user related states to end users.
> Flow level represents summary info of a specific flow. User level aggregation represents summary info of a specific user, it should include summary info of accumulated and statistic means (by two levels: application and flow), like: number of Flows, applications, resource consumption, resource means per app or flow, etc.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org