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 21d658caa HDDS-14553. Update EC doc with correct supported configs. 
(#321)
21d658caa is described below

commit 21d658caa360f368e8653019a4d7481036d95468
Author: Uma Maheswara Rao G <[email protected]>
AuthorDate: Thu Feb 5 09:14:33 2026 -0800

    HDDS-14553. Update EC doc with correct supported configs. (#321)
---
 cspell.yaml                                               | 1 +
 docs/03-core-concepts/02-replication/04-erasure-coding.md | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/cspell.yaml b/cspell.yaml
index 62afb3c2f..b98d7535d 100644
--- a/cspell.yaml
+++ b/cspell.yaml
@@ -241,3 +241,4 @@ words:
 - NVMe
 - ntpd
 - hotswap
+- UDF
diff --git a/docs/03-core-concepts/02-replication/04-erasure-coding.md 
b/docs/03-core-concepts/02-replication/04-erasure-coding.md
index eadbc1927..75254c5ca 100644
--- a/docs/03-core-concepts/02-replication/04-erasure-coding.md
+++ b/docs/03-core-concepts/02-replication/04-erasure-coding.md
@@ -112,7 +112,7 @@ Each EC Replication Config defined by the following pieces 
of information:
 To pass the EC Replication Config in command line or configuration files, we 
need to use the following format:
 *codec*-*num data blocks*-*num parity blocks*-*EC chunk size*
 
-Currently, there are three built-in EC Replication Configs supported: 
`RS-3-2-1024k`, `RS-6-3-1024k`, `XOR-2-1-1024k`.
+Currently, there are three built-in EC Replication Configs supported: 
`RS-3-2-1024k`, `RS-6-3-1024k`, `RS-10-4-1024k`.
 The most recommended option is `RS-6-3-1024k`. When a key/file created without 
specifying the Replication Config,
 it inherits the EC Replication Config of its bucket if it's available.
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to