mirror of
https://github.com/minio/minio.git
synced 2025-02-23 03:22:30 -05:00
clarify maximum number of buckets (#18718)
This commit is contained in:
parent
5fc7da345d
commit
60aff22931
@ -19,7 +19,7 @@ For optimal production setup MinIO recommends Linux kernel version 4.x and later
|
||||
|
||||
| Item | Specification |
|
||||
|:--------------------------------------------------------------------------------|:--------------------------------------------------------------------------------|
|
||||
| Maximum number of buckets | unlimited (we recommend not beyond 500000 buckets) |
|
||||
| Maximum number of buckets | unlimited (we recommend not beyond 500000 buckets) - see NOTE: |
|
||||
| Maximum number of objects per bucket | no-limit |
|
||||
| Maximum object size | 50 TiB |
|
||||
| Minimum object size | 0 B |
|
||||
@ -34,6 +34,8 @@ For optimal production setup MinIO recommends Linux kernel version 4.x and later
|
||||
| Maximum length for '/' separated object name segment | 255 |
|
||||
| Maximum number of versions per object | 10000 (can be configured to higher values but we do not recommend beyond 10000) |
|
||||
|
||||
> NOTE: While MinIO does not implement an upper boundary on buckets, your cluster's hardware has natural limits that depend on the workload and its scaling patterns. We strongly recommend [MinIO SUBNET](https://min.io/pricing) for architecture and sizing guidance for your production use case.
|
||||
|
||||
## List of Amazon S3 API's not supported on MinIO
|
||||
|
||||
We found the following APIs to be redundant or less useful outside of AWS S3. If you have a different view on any of the APIs we missed, please consider opening a [GitHub issue](https://github.com/minio/minio/issues) with relevant details on why MinIO must implement them.
|
||||
|
Loading…
x
Reference in New Issue
Block a user