hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (YARN-3817) [Aggregation] Flow and User level aggregation on Application States table
Date Wed, 22 Jul 2015 18:18:15 GMT

     [ https://issues.apache.org/jira/browse/YARN-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Li Lu reassigned YARN-3817:
---------------------------

    Assignee: Li Lu  (was: Junping Du)

> [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
>
>
> We need flow/user level aggregation to present flow/user related states to end users.
> Flow level aggregation involve three levels aggregations:
> - The first level is Flow_run level which represents one execution of a flow and shows
exactly aggregated data for a run of flow.
> - The 2nd level is Flow_version level which represents summary info of a version of flow.
> - The 3rd level is Flow level which 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)

Mime
View raw message