minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-04-22 19:02:57 +03:00
Code
docs/source/operations/install-deploy-manage/deploy-minio-single-node-multi-drive.rst
Daryl White c676da2376
Adds an admonition for exclusive drive access (#1196) 
Admonition added as an include, then put in many files throughout the
docs.
Where it is included, it's the same admonition and text.

It's worth making sure where I placed the include makes sense.

Closes #1186
2024-04-25 14:19:30 -04:00

2.1 KiB
Raw 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. 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