[
https://issues.apache.org/jira/browse/HDFS-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004467#comment-15004467
]
Vinod Kumar Vavilapalli commented on HDFS-9426:
-----------------------------------------------
Realized there was a follow-up HDFS-8656 to the incompatible change HDFS-7645,
so now not entirely clear which way we should go. IAC, left a comment:
https://issues.apache.org/jira/browse/HDFS-7645?focusedCommentId=15004464&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15004464.
> 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
> 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)
