Distributed MinIO Quickstart Guide Slack Docker Pulls

MinIO in distributed mode lets you pool multiple drives (even on different machines) into a single object storage server. As drives are distributed across several nodes, distributed MinIO can withstand multiple node failures and yet ensure full data protection.

Why distributed MinIO?

MinIO in distributed mode can help you setup a highly-available storage system with a single object storage deployment. With distributed MinIO, you can optimally use storage devices, irrespective of their location in a network.

Data protection

Distributed MinIO provides protection against multiple node/drive failures and bit rot using erasure code. As the minimum disks required for distributed MinIO is 4 (same as minimum disks required for erasure coding), erasure code automatically kicks in as you launch distributed MinIO.

High availability

A stand-alone MinIO server would go down if the server hosting the disks goes offline. In contrast, a distributed MinIO setup with n disks will have your data safe as long as n/2 or more disks are online. You'll need a minimum of (n/2 + 1) disks to create new objects.

For example, an 16-node distributed MinIO setup with 16 disks per node would continue serving files, even if up to 8 servers are offline. But, you'll need at least 9 servers online to create new objects.

You can also use storage classes to set custom data and parity distribution per object.

Consistency Guarantees

MinIO follows strict read-after-write and list-after-write consistency model for all i/o operations both in distributed and standalone modes.

Get started

If you're aware of stand-alone MinIO set up, the process remains largely the same. MinIO server automatically switches to stand-alone or distributed mode, depending on the command line parameters.

1. Prerequisites

Install MinIO - MinIO Quickstart Guide.

2. Run distributed MinIO

To start a distributed MinIO instance, you just need to pass drive locations as parameters to the minio server command. Then, you’ll need to run the same command on all the participating nodes.


Example 1: Start distributed MinIO instance on 32 nodes with 32 drives each mounted at /export1 to /export32 (pictured below), by running this command on all the 32 nodes:

Distributed MinIO, 32 nodes with 32 drives each

GNU/Linux and macOS

minio server http://host{1...32}/export{1...32}

NOTE: {1...n} shown have 3 dots! Using only 2 dots {1..32} will be interpreted by your shell and won't be passed to MinIO server, affecting the erasure coding order, which may impact performance and high availability. Always use ellipses syntax {1...n} (3 dots!) for optimal erasure-code distribution

Expanding existing distributed setup

MinIO supports expanding distributed erasure coded clusters by specifying new set of clusters on the command-line as shown below:

minio server http://host{1...32}/export{1...32} http://host{33...64}/export{1...32}

Now the server has expanded storage of 1024 more disks in total of 2048 disks, new object upload requests automatically start using the least used cluster. This expansion strategy works endlessly, so you can perpetually expand your clusters as needed. When you restart, it is immediate and non-disruptive to the applications. Each group of servers in the command-line is called a zone. There are 2 zones in this example. New objects are placed in zones in proportion to the amount of free space in each zone. Within each zone, the location of the erasure-set of drives is determined based on a deterministic hashing algorithm.

NOTE: Each zone you add must have the same erasure coding set size as the original zone, so the same data redundancy SLA is maintained.
For example, if your first zone was 8 drives, you could add further zones of 16, 32 or 1024 drives each. All you have to make sure is deployment SLA is multiples of original zone i.e 8.

3. Test your setup

To test this setup, access the MinIO server via browser or mc.

Explore Further