From bc9509bc8a95cc35113afe850428bee0d16ff056 Mon Sep 17 00:00:00 2001 From: "Anand Babu (AB) Periasamy" Date: Wed, 30 Nov 2016 01:58:31 -0800 Subject: [PATCH] edits on Limits --- docs/distributed/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/distributed/README.md b/docs/distributed/README.md index 90cd6c639..741fe7aea 100644 --- a/docs/distributed/README.md +++ b/docs/distributed/README.md @@ -16,7 +16,7 @@ A stand-alone Minio server would go down if the server hosting the disks goes of For example, an 8-node distributed Minio setup, with 1 disk per node would stay put, even if upto 4 nodes are offline. But, you'll need atleast 5 nodes online to create new objects. -## Limitations +### Limits As with Minio in stand-alone mode, distributed Minio has a per tenant limit of minimum 4 and maximum 16 drives (imposed by erasure code). This helps maintain simplicity and yet remain scalable. If you need a multiple tenant setup, you can easily spin multiple Minio instances managed by orchestration tools like Kubernetes.