From 377d9659d24a405f43c515d73488f8cf796d164d Mon Sep 17 00:00:00 2001 From: Ravind Kumar Date: Wed, 25 Jan 2023 11:44:16 -0500 Subject: [PATCH] Minor Fix: Remove 0-parity EC reference from EC docs --- source/operations/concepts/erasure-coding.rst | 8 -------- 1 file changed, 8 deletions(-) diff --git a/source/operations/concepts/erasure-coding.rst b/source/operations/concepts/erasure-coding.rst index 89bf529f..a71faa73 100644 --- a/source/operations/concepts/erasure-coding.rst +++ b/source/operations/concepts/erasure-coding.rst @@ -29,14 +29,6 @@ For more complete information on selecting erasure code parity, see :ref:`minio- Use the MinIO `Erasure Code Calculator `__ when planning and designing your MinIO deployment to explore the effect of erasure code settings on your intended topology. -Zero-Parity Deployments ------------------------ - -Starting with :minio-release:`RELEASE.2022-06-02T02-11-04Z`, MinIO supports a Single-Node Single-Drive (SNSD) topology with a zero-parity erasure coding backend. - -Erasure Coding protections do not apply to the zero-parity backend of |SNSD| deployments. -Zero-parity deployments depend on the underlying storage for resiliency and availability. - .. _minio-ec-erasure-set: Erasure Sets