[
https://issues.apache.org/jira/browse/HDFS-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-5920:
----------------------------
Attachment: HDFS-5920.003.patch
Update the patch to address Suresh's comments.
bq. Before merge, we should replcae checks that check startup option is
rollback and upgrade option is rollback to a method on StartupOption. There are
many such checks in NN and DN.
I have not done this change in this patch. I guess maybe we can do it for DN
and NN together (after this and HDFS-5907 get committed).
> Support rollback of rolling upgrade in NameNode and JournalNodes
> ----------------------------------------------------------------
>
> Key: HDFS-5920
> URL: https://issues.apache.org/jira/browse/HDFS-5920
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: journal-node, namenode
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-5920.000.patch, HDFS-5920.000.patch,
> HDFS-5920.001.patch, HDFS-5920.002.patch, HDFS-5920.003.patch
>
>
> This jira provides rollback functionality for NameNode and JournalNode in
> rolling upgrade.
> Currently the proposed rollback for rolling upgrade is:
> 1. Shutdown both NN
> 2. Start one of the NN using "-rollingUpgrade rollback" option
> 3. This NN will load the special fsimage right before the upgrade marker,
> then discard all the editlog segments after the txid of the fsimage
> 4. The NN will also send RPC requests to all the JNs to discard editlog
> segments. This call expects response from all the JNs. The NN will keep
> running if the call succeeds.
> 5. We start the other NN using bootstrapstandby rather than "-rollingUpgrade
> rollback"
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
