This is an automated email from the ASF dual-hosted git repository.
weichiu pushed a commit to branch HDDS-9225-website-v2
in repository https://gitbox.apache.org/repos/asf/ozone-site.git
The following commit(s) were added to refs/heads/HDDS-9225-website-v2 by this
push:
new d09ccd84a HDDS-14342. [Websit v2] [Docs] [Administrator Guide] Migrate
"Calculating EC Pipeline Limits" section (#267)
d09ccd84a is described below
commit d09ccd84abce16301623d66221fb349ea4ceb5d7
Author: Russole <[email protected]>
AuthorDate: Wed Jan 21 11:58:35 2026 +0800
HDDS-14342. [Websit v2] [Docs] [Administrator Guide] Migrate "Calculating
EC Pipeline Limits" section (#267)
---
.../06-calculating-ec-pipeline-limits.md | 39 ++++++++++++++++++++++
1 file changed, 39 insertions(+)
diff --git
a/docs/05-administrator-guide/02-configuration/04-performance/06-calculating-ec-pipeline-limits.md
b/docs/05-administrator-guide/02-configuration/04-performance/06-calculating-ec-pipeline-limits.md
new file mode 100644
index 000000000..a7d83c605
--- /dev/null
+++
b/docs/05-administrator-guide/02-configuration/04-performance/06-calculating-ec-pipeline-limits.md
@@ -0,0 +1,39 @@
+---
+sidebar_label: Calculating EC Pipeline Limits
+---
+
+# Calculating EC Pipeline Limits
+
+The target number of open EC pipelines SCM aims to maintain is calculated
dynamically for each EC replication configuration (e.g., RS-6-3, RS-3-2). The
calculation is based on the following two properties, with the final target
being the greater of the two resulting values.
+
+- `ozone.scm.ec.pipeline.minimum`
+ - **Description**: The guaranteed minimum number of open pipelines to
maintain for each EC configuration, regardless of other factors.
+ - **Default Value**: `5`
+
+- `ozone.scm.ec.pipeline.per.volume.factor`
+ - **Description**: A factor used to calculate a target number of pipelines
based on the total number of healthy volumes across all Datanodes in the
cluster.
+ - **Default Value**: `1.0`
+
+## Calculation Logic
+
+SCM first calculates a volume-based target using the formula:
+`(<pipeline.per.volume.factor> * <total healthy volumes>) / <required nodes
for EC config>`
+
+The final target number of pipelines is then determined by:
+`max(<volume-based target>, <pipeline.minimum>)`
+
+## Example
+
+Consider a cluster with **200 total healthy volumes** across all Datanodes and
an EC policy of **RS-6-3** (which requires 9 nodes).
+
+- `ozone.scm.ec.pipeline.minimum` = **5** (default)
+- `ozone.scm.ec.pipeline.per.volume.factor` = **1.0** (default)
+
+1. The volume-based target is: `(1.0 * 200) / 9 = 22`
+2. The final target is: `max(22, 5) = 22`
+
+SCM will attempt to create and maintain approximately **22** open, RS-6-3 EC
pipelines.
+
+## Production Recommendation
+
+The default values are a good starting point for most clusters. If you have a
very high number of volumes and a write-heavy EC workload, you might consider
slightly increasing the `pipeline.per.volume.factor`. Conversely, for
read-heavy workloads, the default minimum of 5 pipelines is often sufficient.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
