Sangjin Lee commented on YARN-3040:

I am +1 for having a *stable* default value if users didn't set it. The use 
case we're trying to address is a single small cluster setup. If there is a 
timestamp in the default value or it is randomly generated, each time the 
cluster starts up, a new logical cluster is created in the timeline service, 
which is not desirable.

For the most part, we do want users to set this value; e.g. "production", 
"ad-hoc", "science", etc.

> [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

Reply via email to