MinIO AIStor supports publishing bucket notification events to a AMQP 0-9-1 service endpoint such as RabbitMQ. Prerequisites AMQP 0-9-1 service endpoint. MinIO AIStor relies on the https://github.com/streadway/amqp project for AMQP connectivity. The project is primarily tested against RabbitMQ deployments, though other AMQP 0-9-1-compatible services may also work. This procedure assumes a RabbitMQ deployment using the 0-9-1 protocol as the service endpoint.

Use the following examples to help design your own QoS rules. Basic rate limiting The following QoS rule sets a rate limit of 50 s3.PutObject requests per second with a burst of 10. The rule applies to all objects in the bucket and has the highest priority.

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

The MinIO AIStor Console is a rich graphical user interface that provides similar functionality to the mc command line tool. This page provides an overview of the MinIO AIStor Console and describes configuration options and instructions for logging in. Overview You can use the MinIO AIStor Console for administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration.

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.

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.

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

This page provides an overview of AIStor Server deployment architectures from a production perspective. A production AIStor Server deployment consists of at least 4 hosts with homogeneous storage and compute resources. Each AIStor Server host in this pool has matching compute, storage, and network configurations These hosts make up a server pool, where the AIStor Server presents the aggregated compute, memory, and storage as a single resource to clients. Each pool consists of one or more erasure sets.

MinIO AIStor Tables implements native Iceberg tables support in MinIO AIStor object storage. This feature allows you to create, manage, and query Iceberg tables directly through MinIO AIStor with no dependencies on external catalog services or metadata databases. MinIO AIStor Tables is compatible with Iceberg Golang, the Iceberg V3 spec, and the Iceberg REST Catalog. Applications can interact with Iceberg entities through the MinIO AIStor Iceberg API while performing S3 operations through the object storage API.

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.