[
https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745582#comment-14745582
]
Varun Saxena commented on YARN-3816:
------------------------------------
# In TimelineMetric#accumulateTo, can latestMetric be TIME_SERIES ? If
not(seems to be the case as per current code), is the else part of the
condition if (latestMetric.getType().equals(Type.SINGLE_VALUE)) { required ?
# Wont be handling TIME_SERIES then ?
# One of the aggregateMetrics method in TimelineCollector is not required if
you do not plan to use it elsewhere. Agree with Naga that a set should suffice
here.
# Default value can be mentioned explicity for
yarn.timeline-service.aggregation.accumulation.enabled in config file.
# REST API code can be removed I guess if not required for POC.
BTW, the aggregate flag appended into column qualifer will be used by offline
aggregator ?
> [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.1.patch,
> YARN-3816-YARN-2928-v2.2.patch, YARN-3816-YARN-2928-v2.3.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)
