hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9426) Rollingupgrade finalization is not backward compatible
Date Thu, 26 Nov 2015 05:07:11 GMT

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

Hudson commented on HDFS-9426:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #8895 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8895/])
HDFS-9426. Rollingupgrade finalization is not backward compatible (vinayakumarb: rev 9f256d1d716a7e17606245fcfc619901a8fa299a)
* hadoop-hdfs-project/hadoop-hdfs/src/main/proto/DatanodeProtocol.proto
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/DatanodeProtocolServerSideTranslatorPB.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/DatanodeProtocolClientSideTranslatorPB.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt


> 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
>            Assignee: Kihwal Lee
>            Priority: Blocker
>             Fix For: 2.7.2
>
>         Attachments: HDFS-9426.branch-2.7.poc.patch, HDFS-9426.trunk.poc.patch
>
>
> 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.
> NN might have to check the DN version and return different {{rollingUpgradeInfo}}.
> 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
(v6.3.4#6332)

Mime
View raw message