[
https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387462#comment-14387462
]
Zhijie Shen commented on YARN-3391:
-----------------------------------
bq. Then we can apply default values for all (name = YARN app name, version =
1, run id = app submit time)
I propose:
* flow name: String: default(cluster_<appId without "app" prefix>)
* flow version: String: default("1")
* flow run: long: default(1)
The rationale behind flow name default is that for one type of application
(e.g., MR wordcount job), the app name will be the same. Using app name will
group these apps together into one flow.
The rationale behind flow run default is that given an orphan app, we need
always query the app report for the submission time to compose the identifier
(cluster id, user id, flow name, flow version, flow run, app id, entity type,
entity id).
bq. So one option in this case is to reject the submission if the flow id is
set but the flow run id is not set, but there may be better ways of handling
cases like that.
Using 1 for flow run by default shouldn't have the issue, and we don't need to
reject the app for it.
I'm working on a patch, and will post it soon.
> Clearly define flow ID/ flow run / flow version in API and storage
> ------------------------------------------------------------------
>
> Key: YARN-3391
> URL: https://issues.apache.org/jira/browse/YARN-3391
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
>
> To continue the discussion in YARN-3040, let's figure out the best way to
> describe the flow.
> Some key issues that we need to conclude on:
> - How do we include the flow version in the context so that it gets passed
> into the collector and to the storage eventually?
> - Flow run id should be a number as opposed to a generic string?
> - Default behavior for the flow run id if it is missing (i.e. client did not
> set it)
> - How do we handle flow attributes in case of nested levels of flows?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
