[
https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032185#comment-16032185
]
Haibo Chen commented on YARN-6323:
----------------------------------
In rolling upgrade cases where the newer version of YARN cluster has ATSv2
enabled, I think we should try to keep the default flow context for all
applications that did not specify flow information consistent across all NMs
and RM. Otherwise, RM will think application A is in flow X, whereas NMs would
think application A is in flow B, and the result in HBase can be confusing.
I wonder how much value it adds for RM to assign the default flow context based
on application name (in case application name is absent, it falls back to
application id). If that does not matter much, I'd propose both RM and NMs
assign default flow context based on application id.
> 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
