[
https://issues.apache.org/jira/browse/YARN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380443#comment-14380443
]
Zhijie Shen commented on YARN-3040:
-----------------------------------
First, in our use case, we'd like to have a default cluster ID, which is going
to be part of PK to identify the entity object. By having a default, we can
make users to use the timeline service with a simple setup, just as we also
don't require users to come up with a flow ID if it's just an orphan app.
Second, I checked YARN-986 and YARN-1232. It seems not to be clear why it
doesn't make a default before. Anyway to make sure the default doesn't affect
HA logic, I remove the default from yarn-default.xml. Since HA uses
YarnConfiguration#getClusterId, it's separated from the code path we use the
default cluster ID. We can revisit if HA want to have the default cluster ID
set if users don't provide one.
> [Data Model] Make putEntities operation be aware of the app's context
> ---------------------------------------------------------------------
>
> Key: YARN-3040
> URL: https://issues.apache.org/jira/browse/YARN-3040
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Zhijie Shen
> Attachments: YARN-3040.1.patch, YARN-3040.2.patch, YARN-3040.3.patch,
> YARN-3040.4.patch, YARN-3040.5.patch
>
>
> Per design in YARN-2928, implement client-side API for handling *flows*.
> Frameworks should be able to define and pass in all attributes of flows and
> flow runs to YARN, and they should be passed into ATS writers.
> YARN tags were discussed as a way to handle this piece of information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
