MinIO AIStor implements an S3 extension that performs fan-out uploads: writing multiple, independently-readable objects from a single source data stream in one request. Fan-out is an extension to the S3 POST Object (PostUpload) operation. Instead of writing one object per uploaded stream, MinIO AIStor reads the source stream once and creates each object described in the fan-out list. Every created object is a complete, standalone object that you can read afterward using the regular S3 GetObject API.

The following page includes the full contents of the AIStor Server Helm Chart default values.yaml and all accompanying documentation. Removed fields The objectStore.features section (.spec.features in the CRD) has been fully removed in Operator RELEASE.2025-12-16T20-51-03Z. This section includes the following fields that previously provided shortcuts for common configurations.

Memory primarily constrains the number of concurrent simultaneous connections per node. MinIO recommends at least 256GiB of RAM per host. MinIO AIStor allocates up to 75% of host memory to support GET operations. Ensure you size your host memory such that the remaining available host memory supports your target number of concurrent connections per host. You can calculate the maximum number of concurrent requests per node with this formula: $$(0.75 * totalRam) / ramPerRequest$$ramPerRequest is typically 2MiB, which is two times the default erasure block size. For questions about adjusting the erasure block size for your use case, create a SUBNET issue to discuss with MinIO engineers.

This page covers settings that control root (superuser) access for the MinIO AIStor process. The root user has complete access and permissions to perform operations on the MinIO AIStor deployment. Root User and Root Password are required even if you use the MinIO Key Encryption Service or other key management utility. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the MinIO AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.

This page documents settings for configuring a MYSQL service as a target for Bucket Notifications. See Publish Events to MySQL for a tutorial on using these settings. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.

AIStor Server uses the built-in scanner to check objects for healing and to take any scheduled object actions. Such actions may include: calculate data usage on drives evaluate and apply configured lifecycle management or object retention rules perform bucket or site replication check objects for missing or corrupted data or parity shards and perform healing The scanner performs these functions at two levels: cluster and bucket. At the cluster level, the scanner splits all buckets into groups and scans one group of buckets at a time. The scanner starts with any new buckets added since the last scan, then randomizes the scanning of other buckets. The scanner completes checks on all bucket groups before starting over with a new set of scans.

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

jQuery API Documentation Get the value of a computed style property for the first element in the set of matched eleme...

Learn how to configure debugging in Visual Studio Code with launch.json, including attributes, variable substitution, and compound configurations.

Downloads Docs 2.3 2.2 2.1 1.7 main Project Code of conduct Collaboration with Kubernetes SIG-Node Contributing Roadm...