The mc support inspect command collects the data and metadata associated to objects at the specified path. If this information is required to diagnose a SUBNET issue, AIStor Engineering will provide the appropriate command. AIStor assembles this data from each backend drive storing an erasure shard for each specified object. For registered clusters, the file uploads to AIStor for use by the engineering team in support efforts. The command produces an encrypted zip file that includes all matching files with their respective host+drive+path. When writing the zip archive, AIStor also encrypts the zip index of file names included in the archive. The resulting report is intended for use by AIStor Engineering via SUBNET and may contain internal or private data points associated to the object. Exercise caution before sending a report to a third party or posting the report in a public forum.

The mc replicate resync-backlog command triggers replication for backlogged objects by performing HeadObject operations on each unreplicated version. Use this command when replication is stuck or when you need to manually trigger replication for objects with PENDING or FAILED replication status. Syntax Example The following command triggers replication for all backlogged objects in the mybucket bucket on the myaistor alias:

The mc qos rule list command displays all configured Quality of Service (QoS) rules on an AIStor deployment. The command can also be invoked using the short name ls. For more information, see Bucket-level Quality of Service. Syntax Example The following command displays all QoS rules configured for the mybucket bucket on the myaistor deployment:

The mc qos status command displays QoS metrics and status for a specified bucket. Added in RELEASE.2025-12-20T04-58-37Z mc qos status requires AIStor Client RELEASE.2025-12-19T20-11-44Z or later and AIStor Server RELEASE.2025-12-20T04-58-37Z or later. The command displays a table that provides the following QoS metrics:

Description The mc qos rule commands allow you to manage Quality of Service (QoS) rules on an AIStor deployment. QoS rules enable you to control API request rates and concurrency to ensure fair resource allocation and prevent system overload. Rules can be configured based on API operations, bucket patterns, and object prefixes.

The mc support top rpc command displays metrics for remote procedure calls (RPC). You can use key presses to change the sorting of the calls: r sorts by reconnections q sorts by out queue p sorts by ping Syntax Example The following command displays the current remote procedure call metrics for the alias myaistor deployment.

You can configure AIStor Object Store behavior by setting environment variables using the ObjectStore custom resource. The Operator writes these variables to a configuration file accessible by all AIStor Pods in the object store. Overview Version changed Support for valueFrom with configMapKeyRef and secretKeyRef requires Operator version RELEASE.2025-10-16T16-46-38Z or later. The Operator supports two methods for setting environment variables:

This page provides an example that shows how to create an AIStor Tables warehouse and perform basic table operations with the AIStor Client and PyIceberg, a lightweight Python API for interacting with Iceberg Tables. You use the client to create the needed resources and Python code to insert and query data using the AIStor Tables API. You can also call the AIStor Tables API directly, instead of working with the AIStor client commands. See the AIStor Tables API Reference for more information.

Vespa basics Deploy an application Vespa applications Schemas Writing Querying Ranking Operations What's more Learn m...

Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to conten...