[jira] [Updated] (HDFS-8127) NameNode Failover during HA upgrade can cause DataNode to finalize upgrade

["Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated HDFS-8127:
------------------------------------------
    Fix Version/s: 2.6.1

[~sjlee0] backported this to 2.6.1, fixing minor merge conflicts and java diamond operator.

I just pushed the commit to 2.6.1 after running compilation and TestBootstrapStandbyWithQJM, TestDFSUpgradeWithHA which changed in the patch.



> 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
>              Labels: 2.6.1-candidate
>             Fix For: 2.6.1, 2.7.1
>
>         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)