[
https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024242#comment-16024242
]
Rohith Sharma K S commented on YARN-6323:
-----------------------------------------
Thanks Vrushali and Haibo for discussing on rolling upgrade. I have specific
scenario to discuss apart from YARN-6555.
If default context is considered from NM then.
# Application is NOT submitted with tags. So default values are created by
YARN.
## RM creates default FlowContext with FlowName as appName. On NM restart, we
are creating FlowContex with appId. So, there will be a inconsistencies when
entities are published during rolling upgrade.
# Assume that Application is submitted with some tags.
## RM recover the application and start publishing with tags as flow context.
Again there is inconsistencies in published entity.
How are we going to deal with above cases?
> 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: [email protected]
For additional commands, e-mail: [email protected]
