Core Operational Concepts on SILO

Deployment Architecture

Mon, 01 Jan 0001 00:00:00 +0000

This page provides an overview of MinIO deployment architectures from a production perspective. For information on specific hardware or software configurations, see:

Distributed MinIO Deployments

A production MinIO deployment consists of at least 4 MinIO hosts with homogeneous storage and compute resources.

MinIO aggregates these resources together as a pool and presents itself as a single object storage service.

Each MinIO host in this pool has matching compute, storage, and network configurations

MinIO provides best performance when using locally-attached storage, such as NVMe or SSD drives attached to a PCI-E controller board on the host machine.

Availability and Resiliency

Mon, 01 Jan 0001 00:00:00 +0000

This page provides an overview of MinIO’s availability and resiliency design and features from a production perspective.

Note

The contents of this page are intended as a best-effort guide to understanding MinIO’s intended design and philosophy behind availability and resiliency. It cannot replace the functionality of MinIO SUBNET, which allows for coordinating with MinIO Engineering when planning your MinIO deployments.

Community users can seek support on the MinIO Community Slack. Community Support is best-effort only and has no SLAs around responsiveness.

Erasure Coding

Mon, 01 Jan 0001 00:00:00 +0000

Overview of MinIO Erasure Coding

MinIO implements Erasure Coding as a core component in providing data redundancy and availability. This page provides an introduction to MinIO Erasure Coding.

See Availability and Resiliency and Deployment Architecture for more information on how MinIO uses erasure coding in production deployments.

Erasure Coding Basics

Note

The diagrams and content in this section present a simplified view of MinIO erasure coding operations and are not intended to represent the complexities of MinIO’s full erasure coding implementation.

Object Healing

Mon, 01 Jan 0001 00:00:00 +0000

What is healing?

Healing is MinIO’s ability to restore an object that has been damaged, corrupted, or partially lost. The loss can come from multiple types of corruptions or loss, such as but not limited to:

drive-level errors or failure
OS or filesystem errors or failure
bit rot

Healing and Erasure Coding

The ability of MinIO to restore a damaged object relates directly to the following:

total number of drives in the erasure set where the object exists

Object Scanner

Mon, 01 Jan 0001 00:00:00 +0000

Overview

MinIO uses the built-in scanner to check objects for healing and to take any scheduled object actions. Such actions may include:

calculate data usage on drives
evaluate and apply configured lifecycle management or object retention rules
perform bucket or site replication
check objects for missing or corrupted data or parity shards and perform healing

The scanner performs these functions at two levels: cluster and bucket. At the cluster level, the scanner splits all buckets into groups and scans one group of buckets at a time. The scanner starts with any new buckets added since the last scan, then randomizes the scanning of other buckets. The scanner completes checks on all bucket groups before starting over with a new set of scans.

Thresholds and Limits

Mon, 01 Jan 0001 00:00:00 +0000

This page reflects limits and thresholds that apply to MinIO.

Refer to the hardware and software for related recommendations and requirements.

S3 API Limits

Item	Specification
Maximum object size	50 TiB
Minimum object size	0 B
Maximum object size per PUT operation	5 TiB for non-multipart upload 50 TiB for multipart upload
Maximum number of parts per upload	10,000
Part size range