MyFavMirrors/minio
1
0
Fork 0
mirror of https://github.com/minio/minio.git synced 2025-11-07 12:52:58 -05:00
Code Issues Packages Projects Releases Wiki Activity

Clarify behaviour of erasure coding sets (#8745)

Browse Source
This commit is contained in:
Brian Candler
2020-01-05 21:00:11 +00:00
committed by Harshavardhana
parent b9b2b37366
commit 9f44fcd540
2 changed files with 18 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/erasure/README.md
View File

@@ -22,6 +22,14 @@ Bit Rot, also known as data rot or silent data corruption is a data loss issue f
MinIO's erasure coded backend uses high speed [HighwayHash](https://github.com/minio/highwayhash) checksums to protect against Bit Rot.
## How are drives used for Erasure Code?
MinIO divides the drives you provide into erasure-coding sets of 4, 6, 8, 10, 12, 14 or 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 3 sets of 6 drives; but 24 drives are configured as 2 sets of 12 drives.
The drives should all be of approximately the same size.
## Get Started with MinIO in Erasure Code
### 1. Prerequisites