[YARN-6323] Rolling upgrade/config change is broken on timeline v2.

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0, YARN-5355, 3.0.0-beta1, YARN-5355_branch2
• Component/s: timelineserver
• Labels: yarn-5355-merge-blocker
• Hadoop Flags: Reviewed
• Assignee: Vrushali C
• Reporter: Li Lu
• Created: 10/Mar/17 19:49
• Updated: 21/Oct/17 06:05
• Resolved: 21/Aug/17 17:47

Description

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.

Issue Links

• relates to: YARN-6047 Documentation updates for TimelineService v2
• relates to: YARN-6555 Store application flow context in NM state store for work-preserving restart