[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Saxena updated YARN-6323: ------------------------------- Fix Version/s: 2.9.0 > 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: 2.9.0, YARN-5355, 3.0.0-beta1, YARN-5355_branch2 > > Attachments: YARN-6323-YARN-5355.0001.patch, > YARN-6323-YARN-5355.0002.patch, 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.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org