[
https://issues.apache.org/jira/browse/YARN-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478682#comment-15478682
]
Subru Krishnan commented on YARN-5630:
--------------------------------------
bq. But we still have to deal with 2.8 -> 2.7 rollback. Are you suggesting we
introduce an intermediate version that has just the fix for the StateStore
(externalized file / table of keys) move to that version.. and then from there
perform the actual upgrade to 2.8?
Yes as I feel only then is 2.8 -> 2.7 rollback addressed. For practical
reasons, I am fine if we do them separately but feel we should track them
together (in a single rollback umbrella jira).
> 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: [email protected]
For additional commands, e-mail: [email protected]
