You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2015/06/17 16:46:00 UTC

[jira] [Created] (YARN-3815) [Aggregation] Application/Flow/User/Queue Level Aggregations

Junping Du created YARN-3815:
--------------------------------

             Summary: [Aggregation] Application/Flow/User/Queue Level Aggregations
                 Key: YARN-3815
                 URL: https://issues.apache.org/jira/browse/YARN-3815
             Project: Hadoop YARN
          Issue Type: Sub-task
            Reporter: Junping Du
            Assignee: Junping Du
            Priority: Critical


Per previous discussions in some design documents for YARN-2928, the basic scenario is the query for stats can happen on:
- Application level, expect return: an application with aggregated stats
- Flow level, expect return: aggregated stats for a flow_run, flow_version and flow 
- User level, expect return: aggregated stats for applications submitted by user
- Queue level, expect return: aggregated stats for applications within the Queue

Application states is the basic building block for all other level aggregations. We can provide Flow/User/Queue level aggregated statistics info based on application states (a dedicated table for application states is needed which is missing from previous design documents like HBase/Phoenix schema design). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)