[
https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131035#comment-16131035
]
Haibo Chen commented on YARN-6323:
----------------------------------
Agree with [~vrushalic] on that we should focus on fixing the failure on the
upgrade path from no ATS at all to ATSv2. The inconsistencies between flow name
generated by RM and NM for running applications is probably going to be a
limitation. We can file another jira to continue to discuss v1->v2 upgrade
path.
In RM, the flow name is generated by calling
TimelineUtil.generateDefaultFlowName(appName, appId). If appName is null, the
resulting flow name will be like flow_app.getClusterTimestamp()_app.getId().
Can we make it consistent here in NM?
Otherwise, the patch looks good to me.
> Rolling upgrade/config change is broken on timeline v2.
> --------------------------------------------------------
>
> Key: YARN-6323
> URL: https://issues.apache.org/jira/browse/YARN-6323
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Li Lu
> Assignee: Vrushali C
> Labels: yarn-5355-merge-blocker
> Fix For: YARN-5355
>
> Attachments: YARN-6323.001.patch, YARN-6323-YARN-5355.0001.patch
>
>
> Found this issue when deploying on real clusters. If there are apps running
> when we enable timeline v2 (with work preserving restart enabled), node
> managers will fail to start due to missing app context data. We should
> probably assign some default names to these "left over" apps. I believe it's
> suboptimal to let users clean up the whole cluster before enabling timeline
> v2.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
