hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-9426) Rollingupgrade finalization is not backward compatible
Date Fri, 13 Nov 2015 16:05:10 GMT
Kihwal Lee created HDFS-9426:

             Summary: Rollingupgrade finalization is not backward compatible
                 Key: HDFS-9426
                 URL: https://issues.apache.org/jira/browse/HDFS-9426
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Kihwal Lee
            Priority: Blocker

After HDFS-7645, the namenode can return non-null {{rollingUpgradeInfo}} in heatbeat reponses.
2.7.1 or 2.6.x datanodes won't finalize the upgrade because it's not null.

2.7.2rc0 datanodes will finalize the upgrade if the namenode is running 2.7.1 or 2.6, because
it also checks for null {{rollingUpgradeInfo}}.

I believe the quickest fix will be to return null in hearbeat response if rollingupgrade is
not in progress.

HDFS-8656 recognized the compatibility issue of the changed semantics, but unfortunately did
not address the semantics of the heartbeat response.

This message was sent by Atlassian JIRA

View raw message