minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-28 19:42:10 +03:00
Code Activity

Remove incorrect references to downtime on restart

Browse Source
This commit is contained in:
Ravind Kumar
2022-03-03 19:41:34 -05:00
committed by Ravind Kumar
parent 93c9b00cb0
commit 35d0c8250d
20 changed files with 274 additions and 401 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
source/reference/minio-mc-admin/mc-admin-update.rst
View File

@ -21,11 +21,6 @@ environments where the deployment does not have public internet access.
.. end-mc-admin-update-desc
:mc-cmd:`mc admin update` affects *all* MinIO servers in the target deployment
at the same time. The update procedure interrupts in-progress API operations on
the MinIO deployment. Exercise caution before issuing an update command on
production environments.
.. admonition:: Use ``mc admin`` on MinIO Deployments Only
:class: note
@ -33,6 +28,21 @@ production environments.
:start-after: start-minio-only
:end-before: end-minio-only
Considerations
--------------
Updates are Non-Disruptive
~~~~~~~~~~~~~~~~~~~~~~~~~~
:mc-cmd:`mc admin update` updates the binary and restarts all MinIO servers in
the deployment simultaneously. MinIO operations are atomic and strictly
consistent and as such the restart process is non-disruptive to applications.
MinIO strongly recommends only performing simultaneous upgrade-and-restart
procedures. Do not perform "rolling" (e.g one node at a time) upgrade
procedures.
Examples
--------
@ -65,8 +75,7 @@ Syntax
If the specified ``ALIAS`` corresponds to a distributed MinIO
deployment, :mc-cmd:`mc admin update` updates *all* MinIO servers
in the deployment at the same time. The command does not perform a
rolling upgrade or similar zero or near-zero downtime upgrade procedure.
in the deployment at the same time.
Use :mc-cmd:`mc alias list` to review the configured aliases and their
corresponding MinIO deployment endpoints.