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)

AIStor supports hot-swapping failed drives with new healthy drives. Healing AIStor detects and heals those drives without requiring any node or deployment-level restart. AIStor healing occurs only on the replaced drive(s) and in most cases has minimal or negligible impact on deployment performance.

log10(e)

Metrics and Alerts AIStor Server publishes point-in-time metrics using the Prometheus Data Model. You can use any scraping tool which supports that data model to pull those metrics into a database for populating historical views, performing query/analysis of metrics data, or creating alerts on preferred data points.

The Temporal.Duration.from() static method creates a new Temporal.Duration object from another Temporal.Duration object, an object with duration properties, or an ISO 8601 string.

This page documents the installation and management of AIStor object storage using MinIO’s Red Hat OpenShift-certified operator. This procedure assumes that the user interacting with the OpenShift cluster has authorization to: Install Kubernetes operators and associated resources including CustomResourceDefinitions, Statefulsets, and secrets into new or existing namespaces. Perform operations as a user that has broad permissions to create resources within multiple namespaces. Install the AIStor Operator This section installs the OpenShift-certified AIStor Operator. You must complete this section before proceeding to deploying AIStor.

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 primary separator of path components for the current platform.

An `AtomicBool` initialized to `false`.