mc admin update

Description

The mc admin update command updates all MinIO AIStor servers in the deployment.

After running the command, a prompt displays to confirm the update. Type y and [ENTER] to confirm and proceed with the update.

The user must have write permissions for the target location where the binary installs.

This command is intended for updating MinIO AIStor deployments where all installations use the minio binary installation path and do not rely on systemctl, DEB, or RPM packages.

Syntax

Example

Use mc admin update to update each minio server process in the MinIO AIStor deployment:

mc admin update ALIAS

Replace ALIAS with the alias of the MinIO AIStor deployment.

After running the command, answer yes to the prompt to confirm and process the update.

Syntax

mc admin update has the following syntax:

mc admin update ALIAS                  \
                [--bump-api]           \
                [--cancel]             \
                [--dry-run]            \
                [--rolling <duration>] \
                [--status]             \
                [--yes]

mc admin update supports the following arguments:

ALIAS

The alias of the MinIO AIStor deployment to update.

If the specified ALIAS corresponds to a distributed MinIO AIStor deployment, mc admin update updates all MinIO AIStor servers in the deployment at the same time.

Use mc alias list to review the configured aliases and their corresponding MinIO AIStor deployment endpoints.

--bump-api

Optional

Bump the API version on all nodes in the cluster.

When upgrading between MinIO AIStor releases that include API version changes, use this flag after the upgrade completes to synchronize the API version across all nodes. This is a one-time operation per upgrade that does not restart the cluster. Requires confirmation unless --yes is also specified.

The next MinIO AIStor release will perform the API version bump automatically during upgrade. Until then, run this command manually after each upgrade that changes the API version.

--cancel

Optional

Cancel an ongoing cluster update or restart operation.

Use this to stop a rolling update that is currently in progress.

--dry-run

Optional

Preview the update operation without actually performing it. Use this to verify which servers would be updated and to what version.

--rolling

Optional

Perform a rolling update, restarting nodes one at a time with a graceful wait period.

Specify a duration value such as 30s, 1m, or 5m to wait before killing each node. If specified without a value, defaults to 0 (no wait time between restarts).

When using rolling updates, the command displays a TUI showing upgrade progress across all nodes.

--status

Optional

Display the status of an ongoing rolling update.

Use this flag to monitor progress without initiating a new update.

--yes

Alias: -y

Optional

Pass this flag to confirm the update and bypass the confirmation prompt.

Behavior

Updates are non-disruptive

By default, mc admin update updates the binary and restarts all MinIO AIStor servers in the deployment simultaneously. MinIO AIStor operations are atomic and strictly consistent and as such the restart process is non-disruptive to applications.

Rolling updates

Use the --rolling flag to perform a rolling update that restarts nodes one at a time with a configurable grace period. Rolling updates display a TUI showing progress across all nodes.

Use --status to monitor an ongoing rolling update from another terminal, or --cancel to stop the update.

Permissions

The user running the command must have write permissions to the target path where the AIStor Server binary installs.