[
https://issues.apache.org/jira/browse/HDDS-15463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18145774#comment-18145774
]
Sergey Soldatov commented on HDDS-15463:
----------------------------------------
[~sodonnell] The new pipeline is designed and implemented to serve multiple
containers and many clients concurrently, similar to RATIS. As for the fan-out
approach, there are several ways to implement it. The client could handle
fan-out itself, or the first node could forward data to the other two or more
nodes. The benefits largely depend on the deployment model. If clients are
colocated with the DataNodes, this approach could improve overall performance.
However, in a compute-storage architecture, it could introduce additional
network overhead between the compute and storage layers.
> Streaming Write Pipeline without Raft
> -------------------------------------
>
> Key: HDDS-15463
> URL: https://issues.apache.org/jira/browse/HDDS-15463
> Project: Apache Ozone
> Issue Type: New Feature
> Components: Ozone Client, Ozone Datanode
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Labels: pull-request-available
> Attachments: 20260712HDDS-15463 Streaming Write Pipeline without
> Raft.pdf
>
>
> - V1) Raft Pipeline: Use Raft for both WriteChunk and PutBlock
> - V2)Streaming Write Pipeline (HDDS-4454): Use Ratis streaming (RATIS-979)
> for WriteChunk and Raft for PutBlock
> - V3) Streaming Write Pipeline without Raft: Use Ratis streaming for both
> WriteChunk and PutBlock.
> We implement V3 in this JIRA. Will post a design and create subtasks.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]