Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Hide navigatio...

Menu Language en zh Apache Powered By Documentation Getting Started Architecture Tutorials Drill-on-YARN Install Dril...

If an AIStor node suffers complete hardware failure (for example, loss of all drives, data, etc.), the node begins healing operations once it rejoins the deployment. AIStor healing occurs only on the replaced hardware and does not typically impact deployment performance. AIStor healing ensures consistency and correctness of all data restored onto the drive. Changed in RELEASE.2025-02-04T00-52-01Z If multiple drives within the same erasure set require healing, AIStor prioritizes the first drive that begins healing within the erasure set. Other drives in the erasure set wait until healing finishes on the first drive before the next drive starts healing.

AIStor Helm installations consist of two primary parts: The operator chart that controls resources like CustomResourceDefinitions The object-store chart that deploys the AIStor Server You can also upgrade only the AIStor Server image used by a given chart. This page documents a procedure for all three upgrade paths. All 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.

AIStor supports hot-swapping failed drives with new healthy drives. AIStor detects and heals those drives without requiring any node or deployment-level restart. AIStor healing occurs only on the replaced drive(s) and in most cases has minimal or negligible impact on deployment performance. AIStor healing ensures consistency and correctness of all data restored onto the drive. Changed in RELEASE.2025-02-04T00-52-01Z If multiple drives within the same erasure set require healing, AIStor prioritizes the first drive that begins healing within the erasure set. Other drives in the erasure set wait until healing finishes on the first drive before the next drive starts healing.

Generates a metrics scraping configuration file for use with Prometheus. Syntax Example The following command generates a Prometheus scraping configuration file for the deployment at alias myminio:

Lists the entities associated with a policy, user, or group on a target AIStor deployment. This command only returns minio-managed users and groups. To list entities associated with an Active Directory or LDAP (AD/LDAP) configuration, use mc idp ldap policy entities. For example, you can list all of the users and groups attached to a policy or list all of the policies attached to a specific user or group.

Docs » Module code » h2o.utils.shared_utils Source code for h2o.utils.shared_utils #!/usr/bin/env python # -*- encodi...

This page explains how to deploy AIStor with KES for Server Side Encryption. For instructions on running KES, see the KES docs. Broadly, the required steps are: Create a new external key (EK) for server-side encryption (SSE). Create or modify an AIStor deployment to support SSE with KES. Configure automatic bucket-default SSE. Enabling SSE on an AIStor deployment automatically encrypts the backend data for that deployment using the default encryption key.

Description The mc admin accesskey command and its subcommands create and manage Access Keys for internally managed users on an AIStor deployment. Each access key is linked to a user identity and inherits the policies attached to its parent user or those groups in which the parent user has membership. Each access key also supports an optional inline policy which further restricts access to a subset of actions and resources available to the parent user.