Upgrade MinIO AIStor on Linux

This page documents upgrade procedures for AIStor Server clusters on bare-metal Linux infrastructure.

All MinIO 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.

Upgrade MinIO AIStor using DEB or RPM

Use these steps to upgrade an MinIO AIStor cluster where the server process is managed by systemctl, such as those created using the MinIO AIStor DEB/RPM packages.

This procedure assumes you have the MINIO_CONFIG_ENV_FILE variable set on all MinIO AIStor nodes.

  1. Update the MinIO AIStor binary on each node

    Run minio --version on each node to validate that you successfully upgraded all binaries to the same version. Do not proceed unless all nodes use the same MinIO AIStor binary version.

  2. Restart the cluster

    Run the mc admin service restart command to restart all server processes in the cluster simultaneously.

    mc admin service restart ALIAS

    Replace alias of the MinIO AIStor cluster to restart.

    S3-compatible SDKs and applications should retry operations automatically, such that the restart process is typically non-disruptive to ongoing operations.

  3. Validate the upgrade

    Use the mc admin info command to check that all MinIO AIStor servers are online, operational, and reflect the installed MinIO AIStor version.

  4. Upgrade AIStor Client

    Upgrade your mc binary to match or closely follow the server release. You can use the mc update command to update the binary to the latest stable release:

    mc update

Upgrade MinIO AIStor through binary replacement

You can download and manually replace the minio server binary on each of the host nodes in the cluster. You must then restart all nodes simultaneously, such as by using mc admin service restart. This method targets clusters that do not rely on the DEB or RPM packages for installation.

  1. Download the MinIO AIStor binary

    Download the latest stable MinIO AIStor binary for Linux and copies it to /usr/local/bin. The command overwrites the existing minio binary at that path. Use the command appropriate for your host system CPU architecture.

    AMD64

    curl --retry 10 --progress-bar -L  https://dl.min.io/aistor/minio/release/linux-amd64/minio
chmod +x ./minio

    ARM64

    curl --retry 10 --progress-bar -L  https://dl.min.io/aistor/minio/release/linux-arm64/minio
chmod +x ./minio

  2. Replace the older binary

    Move and overwrite the existing binary using root permissions if necessary.

    sudo mv -f ./minio /usr/local/bin/minio

    Repeat for all nodes in the cluster.

  3. Restart the cluster

    Use the mc admin service restart command to restart all nodes in the cluster simultaneously. Rolling or one-at-a-time restarts may produce undesired behavior as nodes start up with incompatible binaries.

    Monitor the status of the cluster using journalctl -uf minio. Once all nodes reach healthy status, you can further validate the upgrade using mc admin info.

  4. Upgrade AIStor Client

    Upgrade your mc binary to match or closely follow the server release. You can use the mc update command to update the binary to the latest stable release:

    mc update

Upgrade MinIO AIStor using CLI commands

The mc admin update supports updating the MinIO AIStor binary on all hosts in the cluster simultaneously. The command requires the following:

  • All host machines must have access to the internet such that they can resolve calls to the dl.min.io subdomain.

  • The system user and group minio-user have write access to the MinIO AIStor minio binary, typically located at /usr/local/bin.

Use chown 775 minio-user:minio-user /usr/local/bin to set the appropriate permissions on all hosts prior to attempting to run the command.

For example, the following command updates a cluster with the alias PRODUCTION:

mc admin update PRODUCTION

The command provides a prompt to confirm the upgrade procedure. Follow the prompt to confirm and start the upgrade. Once completed, the cluster automatically restarts.

Use the mc admin info command to validate the MinIO AIStor version used by the cluster post upgrade.