[
https://issues.apache.org/jira/browse/HDFS-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899644#comment-13899644
]
Jing Zhao commented on HDFS-5889:
---------------------------------
Another issue is that when checkpointing for the rollback image, we did not
rename the md5 file. This can cause failure when loading fsimage for rollback.
We can also fix this in HDFS-5920 since I have both fix and unit test for this
failure.
> 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
> Attachments: h5889_20140211.patch, h5889_20140212b.patch,
> h5889_20140212c.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)
