[
https://issues.apache.org/jira/browse/HDFS-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-6000:
----------------------------
Attachment: HDFS-6000.001.patch
Update the patch. Now the patch can pass all the rolling upgrade related tests.
Main changes made in this patch:
# After entering rolling upgrade, let NN be able to load image from a rollback
image if it has the most recent txid. I.e., we treat the rollback image as
normal image when restarting NN.
# When SBN hits a rolling-upgrade-start editlog, SBN will interrupt the current
standby checkpointer thread and ask it to checkpoint a rollback image.
# After rollback clear the rolling upgrade info in namesystem.
# Load rolling upgrade info from fsimage only if there is a rollback image.
> Avoid saving namespace when starting rolling upgrade
> ----------------------------------------------------
>
> Key: HDFS-6000
> URL: https://issues.apache.org/jira/browse/HDFS-6000
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, ha, hdfs-client, namenode
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-6000.000.patch, HDFS-6000.001.patch
>
>
> Currently when administrator sends the "rollingUpgrade start" command to the
> active NN, the NN will trigger a checkpoint (the rollback fsimage). This will
> cause NN not able to serve for a period of time.
> An alternative way is just to let the SBN do checkpoint, and rename the first
> checkpoint after starting the rolling upgrade to rollback image. After the
> rollback image is on both the ANN and the SBN, administrator can start
> upgrading the software.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
