[
https://issues.apache.org/jira/browse/HDFS-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899661#comment-13899661
]
Suresh Srinivas commented on HDFS-5920:
---------------------------------------
Looks like you are waiting for HDFS-5889 to finish the TODOs in this patch.
Comments:
# nit: "discard unnecessary editlog" -> "discard unnecessary editlog segments"
# nit: trashEditlog() - better name could be discardEditLogSegments() - method
javadoc could say instead of delete, "Discard editlog segments by renaming them
with suffix .trash"?
# "it should be the first txid of some segment" -> "it should be the first txid
of some segment, if segment corresponding to the txid exists"
> 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
>
>
> 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)
