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:

Description The mc admin replicate command creates and manages site replication for a set of AIStor peer sites. Site replication mimics an active-active bucket replication, but for multiple AIStor deployments. Wherever a change occurs to IAM settings, buckets, or objects across the set of sites, the change replicates across all sites in the site replication group.

The mc admin cluster bucket export command exports bucket metadata for use with the (mc admin cluster bucket import) command. You can use this command to manually back up the metadata for the specified AIStor bucket. The command always saves the output as cluster-metadata.zip. If you specify only the deployment as the target, this command backs up all bucket metadata on the target deployment.

Project documentation for Gluster Filesystem

Project documentation for Gluster Filesystem

Project documentation for Gluster Filesystem

Project documentation for Gluster Filesystem

Use the REST API to interact with pull request review comments.

Project documentation for Gluster Filesystem