Docker samples for MariaDB.

Lists all policies on the target AIStor deployment. Syntax Example The following command lists all policies on the deployment at alias myminio.

Description The mc admin cluster bucket command and its subcommands provide tools for manually importing and exporting AIStor bucket metadata. This metadata includes configurations related to features like lifecycle management rules. You can use this metadata as a snapshot of the bucket configuration for restoration later, such as part of or backup/restore operations.

The mc admin user rm command removes an AIStor user on the target AIStor deployment. The mc admin user remove command has equivalent functionality to mc admin user rm. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command removes user myuser on the myminio AIStor deployment:

The mc batch describe command outputs the job definition for a specified job ID. You must specify the job ID. To find the job ID, use mc batch list. Syntax Example The following command outputs the job definition for the job identified as KwSysDpxcBU9FNhGkn2dCf.

Description The mc admin service command can restart or unfreeze AIStor servers. mc admin service affects all AIStor servers in the target deployment at the same time. The command interrupts in-progress API operations on the AIStor deployment. Use caution when issuing this command to a deployment.

Description The mc admin trace command displays API operations occurring on the target AIStor deployment. Example Example Use mc admin trace to monitor API operations on an AIStor deployment:

Example The following command creates a basic YAML file for a replicate job on the mybucket bucket of the myminio alias. mc batch start myminio jobfile.yaml The output of the above command is something similar to: Successfully start 'replicate' job `B34HHqnNMcg1taynaPfxu` on '2022-10-24 17:19:06.296974771 -0700 PDT' Syntax Syntax The command has the following syntax:

The AIStor Batch Framework allows you to create, manage, monitor, and execute jobs using a YAML-formatted job definition file (a “batch file”). The batch jobs run directly on the MinIO deployment to take advantage of the server-side processing power without constraints of the local machine where you run the MinIO Client. A batch file defines one job task. Once started, the AIStor server starts processing the batch job. Time to completion depends on the resources available to the deployment.

Each AIStor server process exposes unauthenticated endpoints for probing server uptime and deployment high availability for simple healthchecks. These endpoints return an HTTP status code indicating whether the underlying resource is healthy or satisfies read/write quorum. The server exposes no other data through these endpoints. AIStor liveness Use the following endpoint to test if the specified AIStor server is up and ready to serve requests: