AIStor supports publishing bucket notification events to a Redis service endpoint. Prerequisites The AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add a Redis endpoint to an AIStor Server The following procedure adds a new Redis service endpoint for supporting bucket notifications in an AIStor Server.

AIStor Server implements Erasure Coding as a core component in providing data redundancy and availability. The diagrams and content in this section present a simplified view of erasure coding operations and are not intended to represent the complexities of the AIStor Server’s full erasure coding implementation. AIStor groups drives in each server pool into one or more Erasure Sets of the same size.

The primary separator of path components for the current platform.

The golden ratio (φ)

Site replication configures multiple independent AIStor deployments as a cluster of replicas called peer sites. Site replication assumes the use of either the included AIStor identity provider (IDP) or an external IDP. All configured deployments must use the same IDP. Deployments using an external IDP must use the same configuration across sites. AIStor does not recommend using macOS, Windows, or non-orchestrated containerized deployments for site replication except for early development, evaluation, or general experimentation.

Distributed AIStor deployments rely on Erasure Coding to provide built-in tolerance for multiple drive or node failures. Depending on the deployment topology and the selected erasure code parity, AIStor can tolerate the loss of up to half the drives or nodes in the deployment while maintaining read access (“read quorum”) to objects. The following table lists the typical types of failure in an AIStor deployment and links to procedures for recovering from each:

log2(10)

This section provides documentation for operating and maintaining AIStor Object Store deployments. Use this documentation for Day 2 and ongoing operational tasks in production environments, including monitoring, scaling, troubleshooting, and managing production AIStor deployments. You can find detailed explanations for core concepts that underpin AIStor. Understanding topics like erasure coding, distributed architecture, and data protection mechanisms provide a foundation for effectively using your cluster. AIStor provides comprehensive monitoring capabilities to maintain reliability and performance. Use metrics, logging, audit trails, and healthcheck endpoints to track deployment health and identify performance bottlenecks.

The following procedure adds a server pool to an existing AIStor cluster running on Kubernetes infrastructure. Each pool expands the total available storage capacity of the cluster with new nodes and persistent volumes while maintaining the overall availability of the cluster. Pay particular attention to the parity (EC:M) value of the existing cluster and the new pool. MinIO strongly recommends seeking an architecture review from MinIO Engineering through SUBNET to analyze potential performance impacts before committing to a new pool for your cluster.

The smallest value that can be represented by this integer type. Use `usize::MIN` instead.