[
https://issues.apache.org/jira/browse/YARN-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484432#comment-15484432
]
Arun Suresh commented on YARN-5630:
-----------------------------------
In that case... +1 for the latest patch..
bq. it adds another user-visible phase to the rollback procedure and places the
burden on admins, requiring them to either know what keys are valid/appropriate
to specify ..
Not necessarily. We can check in a rollback file that contains all new keys
included in every compatible CURRENT_VERSION_INFO which can be scrubbed safely
before rollback.
{code}
....
1.3
/version
1.2
/logDir
/workDir
1.1
/queued
...
{code}
rel 2.8 corresponds to ver 1.3 version info. and rel 2.7 corresponds to 1.0.
The _--prepare-for-rollback_ flag just takes a target version_info argument (in
this case is 1.0). And now we have a list of keys to scrub without any deep
involvement from the admin (Additionally, we can choose to to Key the file with
the release version rather than the CURRENT_VERSION_INFO to make it even easier)
> 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]
