hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8127) NameNode Failover during HA upgrade can cause DataNode to finalize upgrade
Date Tue, 14 Apr 2015 10:18:12 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493870#comment-14493870
] 

Vinayakumar B commented on HDFS-8127:
-------------------------------------

Same/little different problem could occur with the RollingUpgrade also with bootstrapstandby.
Impact may not be this much serious as datanodes will not do finalize if they didnt find rollingupgrade
status

> 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)

Mime
View raw message