Varun Saxena commented on YARN-6323:

Just to put it out there, should we differentiate between these 2 scenarios. I 
mean between momentary writing of entities to both v1 and v2 for rolling 
upgrade and writing to v1 and v2 for comparison or evaluation.
For rolling upgrade scenario, we can possibly write entities for running apps 
only to v1 and from new apps to v2 so we do not get incomplete app data for 
some apps from both v1 and v2.

However, most users may want to try out v2 for a while before they fully switch 
to it. And if we adopt the approach in the sentence above, we may lose data 
from v1, if the user decides to not take up v2.

> 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

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to