Li Lu commented on YARN-3816:

Hi [~djp], I briefly looked at the patch, and have one quick question: In 
application table, we no longer store the type of the incoming entities, IIUC. 
All entity types from the application table will be added in HBaseReader, as in:
        String entityType = isApplication ?
          TimelineEntityType.YARN_APPLICATION.toString() :
In this case, maybe we're missing YARN_APPLICATION_AGGREGATION types and we can 
no longer differentiating them? Or, any other ways we can recognize if an 
entity comes from application itself, or from aggregation? (Am I missing 
anything? )

> [Aggregation] App-level Aggregation for YARN system metrics
> -----------------------------------------------------------
>                 Key: YARN-3816
>                 URL: https://issues.apache.org/jira/browse/YARN-3816
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Junping Du
>            Assignee: Junping Du
>         Attachments: Application Level Aggregation of Timeline Data.pdf, 
> YARN-3816-YARN-2928-v1.patch, YARN-3816-poc-v1.patch, YARN-3816-poc-v2.patch
> We need application level aggregation of Timeline data:
> - To present end user aggregated states for each application, include: 
> resource (CPU, Memory) consumption across all containers, number of 
> containers launched/completed/failed, etc. We need this for apps while they 
> are running as well as when they are done.
> - Also, framework specific metrics, e.g. HDFS_BYTES_READ, should be 
> aggregated to show details of states in framework level.
> - Other level (Flow/User/Queue) aggregation can be more efficient to be based 
> on Application-level aggregations rather than raw entity-level data as much 
> less raws need to scan (with filter out non-aggregated entities, like: 
> events, configurations, etc.).

This message was sent by Atlassian JIRA

Reply via email to