[
https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011262#comment-16011262
]
Haibo Chen commented on YARN-6323:
----------------------------------
Thanks for pointing YARN-6555! I forgot that. A few comments:
bq. /** default version for any flow. */
The semantic for the default flow version will change in YARN-6555. Let's
update it in YARN-6555
Per comment of ApplicationImpl.flowContext, the flow context for an application
is set only if the timeline service v.2 is enabled.
With your change, even when ATSv2 is disabled, a default flow context is set.
How about we return null from recoverFlowContextFromStateStore if ATSv2 is
disabled?
> 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
> Attachments: YARN-6323.001.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.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
