[ 
https://issues.apache.org/jira/browse/YARN-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhijie Shen updated YARN-3041:
------------------------------
    Attachment: YARN-3041.2.patch
                Data_model_proposal_v2.pdf

Based on the online/offline discussion so far around the timeline data model, 
I've updated the proposal doc and attached it hear. Different from the first 
proposal,

* we're going to treat Cluster, Flow, FlowRun, Application, ApplicationAttempt 
and Container as the first class citizen entities. There's parent-child 
relationship among them. FlowRun could be nested.

* In addition, we also define User and Queue to support the aggregation from 
these two aspects.

* Moreover, the metric will host either signal value or time series.

I created and attached a patch, which translates the data model into Java 
objects. It may still need to be adjusted according to JAXB requirement.


> [Data Model] create the ATS entity/event API
> --------------------------------------------
>
>                 Key: YARN-3041
>                 URL: https://issues.apache.org/jira/browse/YARN-3041
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Zhijie Shen
>         Attachments: Data_model_proposal_v2.pdf, YARN-3041.2.patch, 
> YARN-3041.preliminary.001.patch
>
>
> Per design in YARN-2928, create the ATS entity and events API.
> Also, as part of this JIRA, create YARN system entities (e.g. cluster, user, 
> flow, flow run, YARN app, ...).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to