[HDFS-9426] Rollingupgrade finalization is not backward compatible

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.8.0, 2.7.2, 3.0.0-alpha1
• Target Version/s: 2.7.2
• Hadoop Flags: Reviewed
• Assignee: Kihwal Lee
• Reporter: Kihwal Lee
• Created: 13/Nov/15 16:04
• Updated: 05/Jan/17 22:52
• Resolved: 26/Nov/15 04:16

Description

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.

Issue Links

• is broken by: HDFS-7645 Rolling upgrade is restoring blocks from trash multiple times
• is related to: HDFS-8656 Preserve compatibility of ClientProtocol#rollingUpgrade after finalization