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.

Docs » Appendix A - Parameters » prior Edit on GitHub prior Available in: GLM, GAM Hyperparameter: no Description Thi...

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

Docs » Appendix A - Parameters » sample_size Edit on GitHub sample_size Available in: Isolation Forest, Extended Isol...

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.

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

Docs » Appendix A - Parameters » max_depth Edit on GitHub max_depth Available in: GBM, DRF, XGBoost, Isolation Forest...

Docs » Appendix A - Parameters » max_iterations Edit on GitHub max_iterations Available in: GLM, GAM, HGLM, PCA, GLRM...

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.