From c1382c09d9948a19d312a98b8272a4ddefbd994e Mon Sep 17 00:00:00 2001 From: Harshavardhana Date: Mon, 8 Jun 2020 12:30:42 -0700 Subject: [PATCH] add reference to distributed doc for clarity (#9783) --- docs/erasure/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/erasure/README.md b/docs/erasure/README.md index 9d2480251..86aad8731 100644 --- a/docs/erasure/README.md +++ b/docs/erasure/README.md @@ -26,7 +26,7 @@ MinIO's erasure coded backend uses high speed [HighwayHash](https://github.com/m MinIO divides the drives you provide into erasure-coding sets of *4 to 16* drives. Therefore, the number of drives you present must be a multiple of one of these numbers. Each object is written to a single erasure-coding set. -Minio uses the largest possible EC set size which divides into the number of drives given. For example, *18 drives* are configured as *2 sets of 9 drives*, and *24 drives* are configured as *2 sets of 12 drives*. +Minio uses the largest possible EC set size which divides into the number of drives given. For example, *18 drives* are configured as *2 sets of 9 drives*, and *24 drives* are configured as *2 sets of 12 drives*. This is true for scenarios when running MinIO as a standalone erasure coded deployment. In [distributed setup however node (affinity) based](https://docs.minio.io/docs/distributed-minio-quickstart-guide.html) erasure stripe sizes are chosen. The drives should all be of approximately the same size.