Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-7055 YARN Timeline Service v.2: beta 1 / GA
  3. YARN-3815

[Aggregation] Application/Flow/User/Queue Level Aggregations

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Critical
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: timelineserver
    • Labels:

      Description

      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).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                junping_du Junping Du
                Reporter:
                junping_du Junping Du
              • Votes:
                0 Vote for this issue
                Watchers:
                16 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: