[
https://issues.apache.org/jira/browse/YARN-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477609#comment-15477609
]
Jason Lowe commented on YARN-5630:
----------------------------------
Yeah I'm not sure what to do about the schema version. Ideally I'd like to not
bump it unless absolutely necessary. Since we lack any kind of downgrade
script it makes it a permanent, one-way trip for the upgrade. It's already
incompatible today if these keys appear in the state store because it doesn't
recognize them. If later a container runs that did use an increment we're
incompatible while that container is running, but when it completes and the
state is removed from the store then we're compatible again. If we upgrade the
schema version then we're not, even after the containers in question are gone.
Thoughts?
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
