[
https://issues.apache.org/jira/browse/HDFS-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494489#comment-14494489
]
Jing Zhao commented on HDFS-8127:
---------------------------------
RollingUpgrade does not have this issue because instead of using the
bootstrapstandby command, we use an editlog transaction to sync SBN with ANN.
In RollingUpgrade, both SBN and ANN should have the same view about the
rollingupgrade state. {{bootstrapstandby}} is only used for {{-rollingupgrade
rollback}} but I think that should be fine.
> NameNode Failover during HA upgrade can cause DataNode to finalize upgrade
> --------------------------------------------------------------------------
>
> Key: HDFS-8127
> URL: https://issues.apache.org/jira/browse/HDFS-8127
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.4.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Priority: Blocker
> Attachments: HDFS-8127.000.patch, HDFS-8127.001.patch
>
>
> Currently for HA upgrade (enabled by HDFS-5138), we use {{-bootstrapStandby}}
> to initialize the standby NameNode. The standby NameNode does not have the
> {{previous}} directory thus it does not know that the cluster is in the
> upgrade state. If NN failover happens, as response of block reports, the new
> ANN will tell DNs to finalize the upgrade thus make it impossible to rollback
> again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
