This section provides documentation for operating and maintaining MinIO AIStor deployments. Use this documentation for Day 2 and ongoing operational tasks in production environments, including monitoring, scaling, troubleshooting, and managing production MinIO AIStor deployments. Performance and troubleshooting Optimize your deployment with performance tuning guidelines for CPU, memory, storage, and network. Validate your configuration with benchmarking tools. When issues arise, use the debugging and troubleshooting guide for HTTP tracing, diagnostics, and metadata inspection.

Protect MinIO AIStor data directories from accidental deletion using kernel-level storage protection with SELinux or eBPF LSM.

AIStor Server publishes cluster, node, bucket, and resource metrics using the Prometheus Data Model. The procedure on this page documents the following: Configuring a Prometheus service to scrape and display metrics from an AIStor Server deployment Configuring an alert rule on an MinIO AIStor metric to trigger an AlertManager action This tutorial uses metrics version 2. You can also use metrics version 3, which is recommened for new deployments. For more information about version 3, see Metrics and alerts.

MinIO AIStor supports decommissioning and removing server pools from a deployment with two or more pools. To decommission, there must be at least one remaining pool with sufficient available space to receive the objects from the decommissioned pools. MinIO AIStor supports queueing multiple pools in a single decommission command. Each listed pool immediately enters a read-only status, but draining occurs one pool at a time. Decommissioning is designed for removing an older server pool whose hardware is no longer sufficient or performant compared to the pools in the deployment. MinIO AIStor automatically migrates data from the decommissioned pools to the remaining pools in the deployment based on the ratio of free space available in each pool.

AIStor Server publishes its server logs to the system console. These logs can include errors, information output, or other information useful during troubleshooting or debugging. Server logs do not emit for all operations and cannot support audit trail or similar compliance requirements. If you require such a trail, configure and use audit logging instead. You can read the server logs using any of the following methods: Run journalctl -u minio from any host machine. Run mc admin logs against the MinIO AIStor deployment. Record logs to disk New feature — opt-in only Disk-based log recording is a new feature that is disabled by default. Enable it only after thorough testing at scale with your application workload. MinIO is actively optimizing this feature in subsequent releases. MinIO AIStor can record API, error, and audit logs directly to disk as compressed JSON files. This complements webhook-based logging for compliance, forensics, and offline analysis.

This section documents best practices and tutorials for updating the MinIO AIStor server on Linux and Kubernetes infrastructure to a newer release. All MinIO AIStor software supports non-disruptive upgrades with zero downtime. In optimal environments, cluster-wide upgrades typically complete in under 500 milliseconds with large clusters (1000+ nodes) completing in less than 5 seconds. Applications using MinIO or S3 SDKs can rely on the built-in transparent retry to ensure continuous operations during the update procedure.

Manage TLS certificates for MinIO AIStor deployments. TLS certificate management with cert-manager: automate certificate provisioning and renewal using cert-manager issuers Certificate rotation: rotate certificates without downtime on Linux and Kubernetes, monitor expiry with Prometheus TLS certificate troubleshooting: diagnose common TLS errors, inspect certificates, and resolve trust chain issues

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.

Cordon is not always necessary AIStor will correctly remove offline nodes from the cluster automatically. There are normally no additional steps required when taking a node offline for maintenance: just stop the service, perform maintenance and then restart it. For users with certain special requirements, we offer node cordoning as an option. MinIO AIStor allows you to temporarily remove nodes from active service for planned maintenance operations. Removing nodes allows administrators to gracefully take nodes offline without disrupting cluster operations. A cordoned node finishes in-flight operations and marks itself as unavailable for any other operation.

Description The mc admin prometheus command and its subcommands provide access to MinIO Prometheus metrics. Subcommands Subcommand Description generate The mc admin prometheus generate command generates a metrics scraping configuration file for use with Prometheus. metrics The mc admin prometheus metrics command prints Prometheus metrics for a cluster.