hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vrushali C (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.
Date Fri, 12 May 2017 19:21:04 GMT

     [ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vrushali C updated YARN-6323:
-----------------------------
    Attachment: YARN-6323.001.patch

Uploading patch 001.

This patch adds in a default flow context when the NM is trying to recover the app information
upon restart. 

Using the app id itself as the flow name,
a default flow version,
cluster timestamp as flow run id.


> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message