You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Chung En Lee (Jira)" <ji...@apache.org> on 2025/10/21 20:55:03 UTC

[jira] [Updated] (HDDS-3103) Have multi-raft pipeline calculator to recommend best pipeline number per datanode

     [ https://issues.apache.org/jira/browse/HDDS-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chung En Lee updated HDDS-3103:
-------------------------------
    Target Version/s: 2.2.0  (was: 1.2.0)
                      2.2.0  (was: 2.1.0)

<<Bulk update>>
Apache Ozone 2.1.0 release is in progress. I'm updating all unresolved jiras targeting 2.1.0 to retarget 2.2.0.

> Have multi-raft pipeline calculator to recommend best pipeline number per datanode
> ----------------------------------------------------------------------------------
>
>                 Key: HDDS-3103
>                 URL: https://issues.apache.org/jira/browse/HDDS-3103
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: SCM
>    Affects Versions: 0.5.0
>            Reporter: Li Cheng
>            Priority: Major
>              Labels: ozone-jira-volunteer
>
> PipelinePlacementPolicy should have a calculator method to recommend better number for pipeline number per node. The number used to come from ozone.datanode.pipeline.limit in config. SCM should be able to consider how many ratis dir and the ratis retry timeout to recommend the best pipeline number for every node.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org