[
https://issues.apache.org/jira/browse/HDFS-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464552#comment-17464552
]
chuanjie.duan commented on HDFS-5920:
-------------------------------------
[~jingzhao] "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"
Can we keep these editlog segments for replay on rollback_fsimage or startup
with lastest fsimage and old hadoop version.
I mean, "rollback" only rollback hadoop lib version and not lost data
> 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
> Priority: Major
> 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
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
