MinIO AIStor supports expanding an existing distributed cluster by adding a new server pool. Each pool expands the total available storage capacity of the cluster. MinIO AIStor does not support increasing storage through logical volume expansion, rolling drive replacement, or other filesystem-level approaches. Expansion does not provide Business Continuity/Disaster Recovery (BC/DR)-grade protections. While each pool is an independent set of servers with distinct erasure sets for availability, the complete loss of one pool results in MinIO stopping I/O for all pools in the cluster. Similarly, an erasure set which loses quorum in one pool represents data loss of objects stored in that set, regardless of the number of other erasure sets or pools.

This page covers settings for the AIStor Client mc. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.

Learn how to use Docker Debug to troubleshoot Docker Hardened Images (DHI) locally or in production.

Learn how to use Extended Lifecycle Support with Docker Hardened Images.

Get started onboarding your Docker Team or Business organization.

Company FAQs

Vespa basics Deploy an application Vespa applications Schemas Writing Querying Ranking Operations What's more Learn m...

Vespa basics Deploy an application Vespa applications Schemas Writing Querying Ranking Operations What's more Learn m...

Vespa basics Deploy an application Vespa applications Schemas Writing Querying Ranking Operations What's more Learn m...

Vespa basics Deploy an application Vespa applications Schemas Writing Querying Ranking Operations What's more Learn m...