hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.
Date Tue, 22 Aug 2017 10:23:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136606#comment-16136606
] 

Varun Saxena commented on YARN-6323:
------------------------------------

Yeah I will delete it again. I think I checked it in github too when I had deleted it last
time. Anyways will do so again.

> 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: YARN-5355, YARN-5355-branch-2
>
>         Attachments: YARN-6323.001.patch, YARN-6323-YARN-5355.0001.patch, YARN-6323-YARN-5355.0002.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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message