MyFavMirrors/minio
1
0
Fork 0
mirror of https://github.com/minio/minio.git synced 2024-12-25 22:55:54 -05:00
Code Issues Packages Projects Releases Wiki Activity

fix: few typos and wordings in minio-limits.md

Browse Source
This commit is contained in:
Harshavardhana 2023-05-05 20:04:52 -07:00 committed by GitHub
parent 76913a9fd5
commit 824c55b3a4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/minio-limits.md
View File

@ -1,6 +1,6 @@
# MinIO Server Limits Per Tenant # MinIO Server Limits Per Tenant
For best deployment experience MinIO recommends operating systems RHEL/CentOS 8.x or later, Ubuntu 18.04 LTS or later. These operating systems package the latest 'xfsprogs' that support large scale deployments. For optimal production setup MinIO recommends Linux kernel version 4.x and later.
## Erasure Code (Multiple Drives / Servers) ## Erasure Code (Multiple Drives / Servers)
@ -19,13 +19,13 @@ For best deployment experience MinIO recommends operating systems RHEL/CentOS 8.
| Item | Specification | | Item | Specification |
|:--------------------------------------------------------------------------------|:------------------------------------------------| |:--------------------------------------------------------------------------------|:------------------------------------------------|
| Maximum number of buckets | unlimited (recommend not beyond 500000 buckets) | | Maximum number of buckets | unlimited (we recommend not beyond 500000 buckets) |
| Maximum number of objects per bucket | no-limit | | Maximum number of objects per bucket | no-limit |
| Maximum object size | 50 TiB | | Maximum object size | 50 TiB |
| Minimum object size | 0 B | | Minimum object size | 0 B |
| Maximum object size per PUT operation | 5 TiB | | Maximum object size per PUT operation | 5 TiB |
| Maximum number of parts per upload | 10,000 | | Maximum number of parts per upload | 10,000 |
| Part size range | 5 MiB to 5 GiB. Last part can be 0 B to 5 GiB | | Part size range | 5 MiB to 5 TiB. Last part can be 0 B to 5 TiB |
| Maximum number of parts returned per list parts request | 10000 | | Maximum number of parts returned per list parts request | 10000 |
| Maximum number of objects returned per list objects request | 1000 | | Maximum number of objects returned per list objects request | 1000 |
| Maximum number of multipart uploads returned per list multipart uploads request | 1000 | | Maximum number of multipart uploads returned per list multipart uploads request | 1000 |
@ -35,15 +35,14 @@ For best deployment experience MinIO recommends operating systems RHEL/CentOS 8.
## List of Amazon S3 API's not supported on MinIO ## 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 open a [GitHub issue](https://github.com/minio/minio/issues). 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.
### List of Amazon S3 Bucket API's not supported on MinIO ### List of Amazon S3 Bucket API's not supported on MinIO
- BucketACL (Use [bucket policies](https://min.io/docs/minio/linux/administration/identity-access-management/policy-based-access-control.html) instead) - BucketACL (Use [bucket policies](https://min.io/docs/minio/linux/administration/identity-access-management/policy-based-access-control.html) instead)
- BucketCORS (CORS enabled by default on all buckets for all HTTP verbs) - BucketCORS (CORS enabled by default on all buckets for all HTTP verbs, you can optionally restrict the CORS domains)
- BucketWebsite (Use [`caddy`](https://github.com/caddyserver/caddy) or [`nginx`](https://www.nginx.com/resources/wiki/)) - BucketWebsite (Use [`caddy`](https://github.com/caddyserver/caddy) or [`nginx`](https://www.nginx.com/resources/wiki/))
- BucketAnalytics, BucketMetrics, BucketLogging (Use [bucket notification](https://min.io/docs/minio/linux/administration/monitoring/bucket-notifications.html) APIs) - BucketAnalytics, BucketMetrics, BucketLogging (Use [bucket notification](https://min.io/docs/minio/linux/administration/monitoring/bucket-notifications.html) APIs)
- BucketRequestPayment
### List of Amazon S3 Object API's not supported on MinIO ### List of Amazon S3 Object API's not supported on MinIO
@ -53,9 +52,9 @@ We found the following APIs to be redundant or less useful outside of AWS S3. If
- Object name restrictions on MinIO are governed by OS and filesystem limitations. For example object names that contain characters `^*|\/&";` are unsupported on Windows platform or any other file systems that do not support filenames with special charaters. - Object name restrictions on MinIO are governed by OS and filesystem limitations. For example object names that contain characters `^*|\/&";` are unsupported on Windows platform or any other file systems that do not support filenames with special charaters.
> **This list is non exhaustive, it depends on the operating system and filesystem under use - please consult your operating system vendor for a more comprehensiv list**. > **This list is non exhaustive, it depends on the operating system and filesystem under use - please consult your operating system vendor for a more comprehensive list of special characters**.
MinIO recommends using Linux operating system for for production workloads. MinIO recommends using Linux operating system for production workloads.
- Objects must not have conflicting objects as parent objects, applications using this behavior should change their behavior and use non-conflicting unique keys, for example situations such as following conflicting key patterns are not supported. - Objects must not have conflicting objects as parent objects, applications using this behavior should change their behavior and use non-conflicting unique keys, for example situations such as following conflicting key patterns are not supported.