Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 94A6418F88 for ; Wed, 17 Jun 2015 15:35:00 +0000 (UTC) Received: (qmail 68312 invoked by uid 500); 17 Jun 2015 15:35:00 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 68273 invoked by uid 500); 17 Jun 2015 15:35:00 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 68262 invoked by uid 99); 17 Jun 2015 15:35:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2015 15:35:00 +0000 Date: Wed, 17 Jun 2015 15:35:00 +0000 (UTC) From: "Junping Du (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3817) [Aggregation] Flow and User level aggregation on Application States table MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589932#comment-14589932 ] Junping Du commented on YARN-3817: ---------------------------------- Upload proposal for flow and user aggregation in detail. Comments are welcomed! > [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: Junping Du > 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)