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 "Li Lu (JIRA)" <ji...@apache.org> on 2015/08/28 03:07:46 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14717861#comment-14717861 ] 

Li Lu commented on YARN-3817:
-----------------------------

Oh BTW the patch is based on YARN-3816-YARN-2928-v1.patch in YARN-3816. 

> [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
>         Attachments: Detail Design for Flow and User Level Aggregation.pdf, 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
(v6.3.4#6332)