- Sort Score
- Result 10 results
- Languages All
- Labels All
Results 151 - 160 of 480 for host:docs.min.io (0.1 sec)
-
Healthcheck Probes | AIStor Object Store Docume...
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:docs.min.io/enterprise/aistor-object-store/operations/monitoring/healthcheck-probe/Registered: Fri Jan 16 05:02:52 UTC 2026 - Last Modified: Wed Jan 14 19:11:19 UTC 2026 - 260.3K bytes - Viewed (0) -
Publish Events to Elasticsearch | AIStor Object...
AIStor Server supports publishing bucket notification events to an Elasticsearch service endpoint. Prerequisites Elasticsearch v7.0 or later. AIStor relies on the v7 project for Elastic connectivity. The elastic/v7 library specifically targets Elasticsearch v7.0 and is not compatible with earlier Elasticsearch versions. The AIStor mc command line tool.docs.min.io/enterprise/aistor-object-store/administration/bucket-notifications/publish-events-to-...Registered: Fri Jan 16 05:03:22 UTC 2026 - Last Modified: Wed Jan 14 19:11:18 UTC 2026 - 278.6K bytes - Viewed (0) -
Batch Framework | AIStor Object Store Documenta...
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.docs.min.io/enterprise/aistor-object-store/administration/batch-framework/Registered: Fri Jan 16 05:03:41 UTC 2026 - Last Modified: Wed Jan 14 19:11:18 UTC 2026 - 260.4K bytes - Viewed (0) -
Upgrade | AIStor Object Store Documentation
This section documents best practices and tutorials for updating the AIStor server on Linux and Kubernetes infrastructure to a newer release. 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. Applications using MinIO or S3 SDKs can rely on the built-in transparent retry to ensure continuous operations during the update procedure.docs.min.io/enterprise/aistor-object-store/upgrade-aistor-server/Registered: Fri Jan 16 05:05:56 UTC 2026 - Last Modified: Wed Jan 14 19:11:19 UTC 2026 - 261K bytes - Viewed (0) -
mc admin prometheus | AIStor Object Store Docum...
Description The mc admin prometheus command and its subcommands provide access to MinIO Prometheus metrics. Subcommands Subcommand Description generate The mc admin prometheus generate command generates a metrics scraping configuration file for use with Prometheus. metrics The mc admin prometheus metrics command prints Prometheus metrics for a cluster.docs.min.io/enterprise/aistor-object-store/reference/cli/admin/mc-admin-prometheus/Registered: Fri Jan 16 05:06:00 UTC 2026 - Last Modified: Wed Jan 14 19:11:19 UTC 2026 - 253.4K bytes - Viewed (0) -
mc admin service | AIStor Object Store Document...
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.docs.min.io/enterprise/aistor-object-store/reference/cli/admin/mc-admin-service/Registered: Fri Jan 16 05:07:50 UTC 2026 - Last Modified: Wed Jan 14 19:11:19 UTC 2026 - 258.6K bytes - Viewed (0) -
mc admin policy rm | AIStor Object Store Docume...
Removes an IAM policy from the target AIStor deployment. Syntax Example The following command removes the policy readonly from the deployment at alias myaistor.docs.min.io/enterprise/aistor-object-store/reference/cli/admin/mc-admin-policy/mc-admin-policy-re...Registered: Fri Jan 16 05:07:53 UTC 2026 - Last Modified: Wed Jan 14 19:11:19 UTC 2026 - 257.5K bytes - Viewed (0) -
mc admin replicate | AIStor Object Store Docume...
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.docs.min.io/enterprise/aistor-object-store/reference/cli/admin/mc-admin-replicate/Registered: Fri Jan 16 05:07:59 UTC 2026 - Last Modified: Wed Jan 14 19:11:19 UTC 2026 - 309K bytes - Viewed (0) -
mc admin object info | AIStor Object Store Docu...
Description mc admin object info displays a summary of part and shard information about a specified object. The output includes information for each part or shard of the object, including: Part number Pool number Node Erasure set Drive Filename Size By default, the output uses a set of gridded blocks to indicate the parts of object. Colors indicate the status of the specific part.docs.min.io/enterprise/aistor-object-store/reference/cli/admin/mc-admin-object-info/Registered: Fri Jan 16 05:08:16 UTC 2026 - Last Modified: Wed Jan 14 19:11:19 UTC 2026 - 264.5K bytes - Viewed (0) -
mc admin info | AIStor Object Store Documentation
The mc admin info command displays information on an AIStor server. For distributed AIStor deployments, mc admin info displays information for each node in the deployment. The output of the command resembles the following for a four-node cluster: ● node1.example.com:9000 Uptime: 3 days Version: 2025-01-01T00-00-00Z Network: 4/4 OK Drives: 4/4 OK Pool: 1 ● node2.example.com:9000 Uptime: 3 days Version: 2025-01-01T00-00-00Z Network: 4/4 OK Drives: 4/4 OK Pool: 1 ● node3.example.com:9000 Uptime: 3 days Version: 2025-01-01T00-00-00Z Network: 4/4 OK Drives: 4/4 OK Pool: 1 ● node4.example.com:9000 Uptime: 3 days Version: 2025-01-01T00-00-00Z Network: 4/4 OK Drives: 4/4 OK Pool: 1 Pools: 1st, Erasure sets: 1, Drives per erasure set: 16 1.5 TiB Used, 12 Buckets, 48000 Objects 16 drives online, 0 drives offline, EC:4 Syntax Example The following command displays AIStor server information for the alias myaistor:docs.min.io/enterprise/aistor-object-store/reference/cli/admin/mc-admin-info/Registered: Fri Jan 16 05:08:36 UTC 2026 - Last Modified: Wed Jan 14 19:11:19 UTC 2026 - 265K bytes - Viewed (0)