[
https://issues.apache.org/jira/browse/HDFS-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904568#comment-13904568
]
Arpit Agarwal commented on HDFS-5889:
-------------------------------------
This patch seems to have broken the rolling upgrade tests.
The new edit log ops {{OP_ROLLING_UPGRADE_START}} and
{{OP_ROLLING_UPGRADE_FINALIZE}} trigger a {{RollingUpgradeException}} during NN
restart. I think the fix should be to invoke
{{startRollingUpgrade/finalizeRollingUpgrade}} (and write to editLog only when
invoked via RPC).
I filed HDFS-5960.
> When rolling upgrade is in progress, standby NN should create checkpoint for
> downgrade.
> ---------------------------------------------------------------------------------------
>
> Key: HDFS-5889
> URL: https://issues.apache.org/jira/browse/HDFS-5889
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Fix For: HDFS-5535 (Rolling upgrades)
>
> Attachments: h5889_20140211.patch, h5889_20140212b.patch,
> h5889_20140212c.patch, h5889_20140213.patch
>
>
> After rolling upgrade is started and checkpoint is disabled, the edit log may
> grow to a huge size. It is not a problem if rolling upgrade is finalized
> normally since NN keeps the current state in memory and it writes a new
> checkpoint during finalize. However, it is a problem if admin decides to
> downgrade. It could take a long time to apply edit log. Rollback does not
> have such problem.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
