[HDDS-9884] DataNode doesn't set proper DatanodeVersion when registering with SCM

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: HDDS-7593
• Labels: pull-request-available
• Assignee: Siyao Meng
• Reporter: Wei-Chiu Chuang
• Created: 08/Dec/23 18:50
• Updated: 15/Feb/24 17:14
• Resolved: 15/Feb/24 17:14

Description

DataNode has a version defined by DatanodeVersion. This is different from ContainerLayoutVersion,
HDDSVolumeLayoutVersion or HDDSLayoutFeature.
 
DatanodeVersion is supposed to be carrried inside DatanodeDetails (initialVersion and currentVersion) but they are not when Datanode register with SCM, so SCM doesn't know the DataNode version. Therefore, client doesn't know.
 
This would need to be fixed to allow new clients talking to old DataNode without blowing up old DataNode. New clients should be able to tell the DataNodes are old and do not send new types of requests.

Issue Links

• relates to: HDDS-9751 [hsync] Make Putblock performance acceptable - DataNode side
• links to: GitHub Pull Request #6155