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

AIStor Server implements Erasure Coding as a core component in providing data redundancy and availability. The diagrams and content in this section present a simplified view of erasure coding operations and are not intended to represent the complexities of the AIStor Server’s full erasure coding implementation. MinIO AIStor groups drives in each server pool into one or more Erasure Sets of the same size. By default, each erasure set can contain 2 to 16 drives. You can configure erasure sets up to 32 drives with the MINIO_ERASURE_SET_DRIVE_COUNT environment variable if running AIStor Server RELEASE.2026-02-02T23-40-11Z or later.

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

MinIO AIStor subscription customers can receive hotfix releases that backport critical fixes to a specific release version without requiring a full upgrade. Hotfixes allow production environments to remain on a standardized release while receiving targeted patches for bugs, regressions, and security vulnerabilities. What is a hotfix A hotfix is a custom build of MinIO AIStor based on a specific release tag with one or more targeted patches cherry-picked from the upstream codebase. Hotfix releases use the naming convention RELEASE.<date>.hotfix to indicate which base release they are built from.

AIStor Server publishes cluster and node metrics using the Prometheus Data Model. You can use any scraping tool to pull metrics data from AIStor Server for further analysis and alerting. This page covers metrics version 3, which has additional metrics and endpoints. Existing deployments can continue to use version 2 metrics. Version 3 endpoints The base endpoint, without an added path, returns cluster, node, and per-bucket statistic metrics from /cluster/usage/buckets.

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

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

The MinIO AIStor Operator supports cert-manager to provision and manage certificates, as an alternative to the Operator. cert-manager obtains valid certificates from an Issuer or ClusterIssuer and can automatically renew certificates prior to expiration. A ClusterIssuer issues certificates for multiple Namespaces. An Issuer only mints certificates for its own Namespace. The following instructions implement a self-signed Cluster Issuer. You can also work with other issuers supported by cert-manager. With other issuers, you must provide the Issuer CA certificate to MinIO AIStor, instead of the CAs mentioned in this guide. This example will use cert-manager to issue cluster certificates. The same procedure can be used to issue certificates that can be used outside the cluster. It’s also allowed to let AIStor Operator generate the cluster certificates and use cert-manager to issue the other certificates. Make sure to keep .spec.certificates.disableAutoCert: false to ensure that AIStor Operator will generate the cluster certificates. Summary You complete the following steps to manage your TLS certificates with cert-manager:

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

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