hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5630) NM fails to start after downgrade from 2.8 to 2.7
Date Sat, 10 Sep 2016 00:23:20 GMT

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

Arun Suresh commented on YARN-5630:
-----------------------------------

Agreed. Another option to maybe consider is have an external script (or maybe even start the
NodeManager using a special _--prepare-for-rollback_ arg) which takes a list of allowed keys,
iterates through all the entries in the LevenDb store and scrub entries with keys not in the
provided list.
This also allows us to make the fix in our target (2.8) version.

> NM fails to start after downgrade from 2.8 to 2.7
> -------------------------------------------------
>
>                 Key: YARN-5630
>                 URL: https://issues.apache.org/jira/browse/YARN-5630
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Blocker
>         Attachments: YARN-5630.001.patch, YARN-5630.002.patch
>
>
> A downgrade from 2.8 to 2.7 causes nodemanagers to fail to start due to an unrecognized
"version" container key on startup.  This breaks downgrades from 2.8 to 2.7.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
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