minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-08-05 03:41:24 +03:00
Code Activity
Files
enterprise
docs/source/operations/install-deploy-manage/deploy-minio-single-node-multi-drive.rst
Ravind Kumar 67e81ce2f8 Multiple SERVER Releases (#1141) 
MinIO SERVER RELEASE.2024-01-05T22-17-24Z - added new metrics to
github.com/minio/minio for later sync

MinIO SERVER RELEASE.2024-01-28T22-35-53Z - MinIO preallocates memory,
mc update compresses binary in transit MinIO SERVER
RELEASE.2024-02-06T21-36-22Z -

MinIO adds condition key for restricting STS AssumeRoleWithWebIdentity
duration at policy level

Closes #1124 , 

Partially addresses #1116 
Partially Addresses #1105


---------

Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
2024-03-11 10:06:46 -04:00

1.9 KiB
Raw Permalink Blame History

Deploy MinIO: Single-Node Multi-Drive

minio

Table of Contents

The procedures on this page cover deploying MinIO in a Single-Node Multi-Drive (SNMD) configuration. |SNMD| deployments provide drive-level reliability and failover/recovery with performance and scaling limitations imposed by the single node.

linux or macos or windows

For production environments, MinIO strongly recommends deploying with the Multi-Node Multi-Drive (Distributed) <minio-mnmd> topology for enterprise-grade performance, availability, and scalability.

container

For production environments, MinIO strongly recommends using the MinIO Kubernetes Operator to deploy Multi-Node Multi-Drive (MNMD) or "Distributed" Tenants.

Prerequisites

Storage Requirements

Memory Requirements

RELEASE.2024-01-28T22-35-53Z

MinIO pre-allocates 2GiB of system memory at startup.

MinIO recommends a minimum of 32GiB of memory per host. See minio-hardware-checklist-memory for more guidance on memory allocation in MinIO.

Deploy Single-Node Multi-Drive MinIO

The following procedure deploys MinIO consisting of a single MinIO server and a multiple drives or storage volumes.

linux

macos

container