mirror of
https://github.com/pgsty/minio.git
synced 2026-08-09 15:53:28 +03:00
Feng Ruohang
fd2ca1c6d2
README, README_ZH, SECURITY, COMPLIANCE, CONTRIBUTING, NOTICE, code_of_conduct, the vulnerability and PR-etiquette documents, the GitHub issue and pull request templates, and the docs/ tree all present Silo as the product. The Grafana dashboards under docs/metrics/prometheus/grafana/ have their panel titles and descriptions rebranded while every minio_* query, label and expression is left alone, so existing alerts and recording rules keep matching. The distinction the review demanded is applied per hit rather than by search-and-replace: - Product and command text becomes Silo and silo: install and run instructions, systemd examples, compose services, download links, badges. - Protocol and interface text keeps MinIO: MINIO_* variables, minio_* metrics, x-minio-* headers, /minio/* routes, .minio.sys, arn:minio, and API field and error names. - Attribution keeps MinIO and gains the fork's own: the AGPL obligations, original copyright, CREDITS and NOTICE stay, with the modification notice added alongside rather than replacing them. - Historical and third-party references are left as facts, not rewritten for brand tidiness. README and README_ZH each carry an explicit non-affiliation notice, document the side-by-side package migration including the /etc/systemd/system/silo.service.d/10-legacy-user.conf drop-in for keeping a legacy UID/GID, and state that recursive chown is never performed. The trademark attribution uses the policy's approved "based on MinIO technology" wording, not the shortened form the policy rejects. github.com/pgsty/minio links are left in place and labelled transitional. The repository has not been renamed, and rewriting them now would produce documented URLs that 404 until the cutover; they change in the cutover commit together with the goreleaser release target, the OCI source label and the raw-content branch. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
40 lines
3.9 KiB
Markdown
40 lines
3.9 KiB
Markdown
# Erasure code sizing guide
|
|
|
|
## Toy Setups
|
|
|
|
Capacity constrained environments, Silo will work but not recommended for production.
|
|
|
|
| servers | drives (per node) | stripe_size | parity chosen (default) | tolerance for reads (servers) | tolerance for writes (servers) |
|
|
|--------:|------------------:|------------:|------------------------:|------------------------------:|-------------------------------:|
|
|
| 1 | 1 | 1 | 0 | 0 | 0 |
|
|
| 1 | 4 | 4 | 2 | 0 | 0 |
|
|
| 4 | 1 | 4 | 2 | 2 | 1 |
|
|
| 5 | 1 | 5 | 2 | 2 | 2 |
|
|
| 6 | 1 | 6 | 3 | 3 | 2 |
|
|
| 7 | 1 | 7 | 3 | 3 | 3 |
|
|
|
|
## Minimum System Configuration for Production
|
|
|
|
| servers | drives (per node) | stripe_size | parity chosen (default) | tolerance for reads (servers) | tolerance for writes (servers) |
|
|
|--------:|------------------:|------------:|------------------------:|------------------------------:|-------------------------------:|
|
|
| 4 | 2 | 8 | 4 | 2 | 1 |
|
|
| 5 | 2 | 10 | 4 | 2 | 2 |
|
|
| 6 | 2 | 12 | 4 | 2 | 2 |
|
|
| 7 | 2 | 14 | 4 | 2 | 2 |
|
|
| 8 | 1 | 8 | 4 | 4 | 3 |
|
|
| 8 | 2 | 16 | 4 | 2 | 2 |
|
|
| 9 | 2 | 9 | 4 | 4 | 4 |
|
|
| 10 | 2 | 10 | 4 | 4 | 4 |
|
|
| 11 | 2 | 11 | 4 | 4 | 4 |
|
|
| 12 | 2 | 12 | 4 | 4 | 4 |
|
|
| 13 | 2 | 13 | 4 | 4 | 4 |
|
|
| 14 | 2 | 14 | 4 | 4 | 4 |
|
|
| 15 | 2 | 15 | 4 | 4 | 4 |
|
|
| 16 | 2 | 16 | 4 | 4 | 4 |
|
|
|
|
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.
|