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 "Junping Du (JIRA)" <ji...@apache.org> on 2015/09/02 02:30:46 UTC
[jira] [Commented] (YARN-3816) [Aggregation] App-level Aggregation
for YARN system metrics
[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726476#comment-14726476 ]
Junping Du commented on YARN-3816:
----------------------------------
Nice catch, [~gtCarrera9]! For now, YARN_APPLICATION_AGGREGATION is almost treated as type of YARN_APPLICATION and only be used to differentiate app aggregated metric with entity metric, but cannot differentiate with app metric. Later, we will differentiate (recover YARN_APPLICATION_AGGREGATION entity) in read path but that need cell tag support. Let's address this in YARN-4053 or afterwards. Make sense?
> [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-YARN-2928-v2.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
(v6.3.4#6332)