[HDDS-9767] Support passing client address to SCM during write

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.4.0
• Component/s: OM, SCM
• Labels: pull-request-available
• Assignee: Ivan Andika
• Reporter: Ivan Andika
• Created: 24/Nov/23 02:35
• Updated: 20/Dec/23 07:52
• Resolved: 07/Dec/23 16:19

Description

In the Write Pipeline V1 (Async), the topology of the write pipeline is not relevant since the write will always go to the leader regardless.

However, with the support of Streaming Write Pipeline (Write Pipeline V2), the topology of the datanodes in the pipeline needs to be considered to build the optimal pipeline.

This patch will support OM to pass clientMachineString to SCM to get the sorted datanodes.

Issue Links

• causes: HDDS-9971 Fix issues in allocateBlock when clientMachine is null
• is related to: HDDS-9392 Streaming write pipeline should pick the nearest datanode as primary node
• is related to: HDDS-9848 Pipeline.nodesInOrder should not be ThreadLocal
• is related to: HDDS-9867 Support topology awareness in pipeline choose policy
• links to: GitHub Pull Request #5666