Skip to content

Minio Sizing #24

@bwalsh

Description

@bwalsh

User Story

As an ACED devops engineer, in order to plan for local storage, I need to know the recommended configuration for S3 compatible, local, premises storage.

Summary

Details

Timeframe
  • MinIO generally recommends planning capacity such that server pool expansion is only required after 2+ years of deployment uptime.

  • More capacity initially is preferred over frequent just-in-time expansion to meet capacity requirements.

Operating Systems

MinIO provides builds of the MinIO server (minio) and the MinIO CLI (mc) for the following platforms.

  • Red Hat Enterprise Linux 8.5+ (including all binary-compatible RHEL alternatives)
  • Ubuntu 18.04+

more

Hardware / VM Type

Homogeneous Node Configurations
MinIO strongly recommends selecting substantially similar hardware configurations for all nodes in the deployment.

Networking and Firewalls
  • Network access
    Each node should have full bidirectional network access to every other node in the deployment.

For example, the following command explicitly opens the default MinIO server API port 9000 for servers running firewalld :

firewall-cmd --permanent --zone=public --add-port=9000/tcp
firewall-cmd --reload
  • Sequential Hostnames
    MinIO requires using expansion notation {x...y} to denote a sequential series of MinIO hosts when creating a server pool. MinIO therefore requires using sequentially-numbered hostnames to represent each minio server process in the deployment.

Create the necessary DNS hostname mappings prior to starting this procedure. For example, the following hostnames would support a 4-node distributed deployment:

aced-ohsu-minio1.example.com
aced-ohsu-minio2.example.com
aced-ohsu-minio3.example.com
aced-ohsu-minio4.example.com

aced-ucl-minio1.example.com
aced-ucl-minio2.example.com
aced-ucl-minio3.example.com
aced-ucl-minio4.example.com

Capacity
  • Disks

Metric Missing: XX/TB per year - assume 10TB.

For example, consider an application suite that is estimated to produce 10TB of data per year. The MinIO deployment should provide at minimum:

10TB + 10TB + 10TB = 30TB

See Sequential Mounts

  • Memory & CPUs

Each host should have a minimum of:

vCPUs Memory
2 4.0GB

References

Minio Website
Minio on AWS
Multi Node Minio in docker compose

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions