[
https://issues.apache.org/jira/browse/HDFS-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE resolved HDFS-6031.
------------------------------------------
Resolution: Fixed
Fix Version/s: HDFS-5535 (Rolling upgrades)
Hadoop Flags: Reviewed
Thanks Haohui, for testing and reviewing the patch.
I have committed this.
> NN running newer software rejects loading the fsimage during rolling upgrade.
> -----------------------------------------------------------------------------
>
> Key: HDFS-6031
> URL: https://issues.apache.org/jira/browse/HDFS-6031
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Haohui Mai
> Assignee: Tsz Wo (Nicholas), SZE
> Fix For: HDFS-5535 (Rolling upgrades)
>
> Attachments: h6031_20140227.patch, h6031_20140227b.patch,
> h6031_20140227c.patch, h6031_20140227d.patch, h6031_20140227e.patch
>
>
> During rolling upgrade, the standby NN that has a newer layout version will
> complain about that the fsimage is too old, and require starting the NN using
> the {{-upgrade}} option:
> {noformat}
> File system image contains an old layout version -55. An upgrade to version
> -56 is required.
> {noformat}
> However, {{-upgrade}} is disabled during rolling upgrade, thus it is
> impossible to restart the standby NN:
> {noformat}
> org.apache.hadoop.hdfs.protocol.RollingUpgradeException: Failed to upgrade
> namenode since a rolling upgrade is already in progress. Existing rolling
> upgrade info:
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
