Back to Minio

Erasure code sizing guide

docs/distributed/SIZING.md

latest3.9 KB
Original Source

Erasure code sizing guide

Toy Setups

Capacity constrained environments, MinIO will work but not recommended for production.

serversdrives (per node)stripe_sizeparity chosen (default)tolerance for reads (servers)tolerance for writes (servers)
111000
144200
414221
515222
616332
717333

Minimum System Configuration for Production

serversdrives (per node)stripe_sizeparity chosen (default)tolerance for reads (servers)tolerance for writes (servers)
428421
5210422
6212422
7214422
818443
8216422
929444
10210444
11211444
12212444
13213444
14214444
15215444
16216444

If one or more drives are offline at the start of a PutObject or NewMultipartUpload operation the object will have additional data protection bits added automatically to provide the regular safety for these objects up to 50% of the number of drives. This will allow normal write operations to take place on systems that exceed the write tolerance.

This means that in the examples above the system will always write 4 parity shards at the expense of slightly higher disk usage.