minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-30 07:03:26 +03:00
Code Activity

DOCS-1190: RELEASE.2024-04-18T19-09-19Z (#1215)

Browse Source 
Partially addresses #1190 

No staged build unless someone requests it.

# Summary

After some thinking, we've leaned towards just making a note of the
upgrade step and calling it done. We do not typically make extended
discussion of backward-breaking changes at this time, and have no where
to keep that sort of guidance.

Maybe in the future or as part of a larger re-arch we can consider where
we would best keep that kind of guidance.

As far as the rest:

- We are not covering s3zip today, so that's a no-op. We should leave
the ticket open in the event we have bandwidth to document the feature
later
- No changes to Console that need documentation at this time
- Added a quick callout on the warning behavior to the Versioning page
- Metrics v3 is also still In progress, come back to this once the
project is fully baked.
This commit is contained in:
Ravind Kumar
2024-05-10 18:16:49 -04:00
committed by GitHub
parent 2953b54ecd
commit 775e99d47b
7 changed files with 27 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
source/includes/linux/common-installation.rst
View File

@ -198,7 +198,7 @@ operating systems using RPM, DEB, or binary:
wget https://dl.min.io/server/minio/release/linux-amd64/minio
chmod +x minio
sudo mv minio /usr/local/bin/
sudo mv -f ./minio /usr/local/bin/minio
Replace ``/usr/local/bin`` with the location of the existing MinIO
binary. Run ``which minio`` to identify the path if not already known.

11
source/includes/linux/steps-upgrade-minio-deployment.rst
View File

@ -63,17 +63,20 @@ Update ``systemctl``-Managed MinIO Deployments
Use these steps to upgrade a MinIO deployment where the MinIO server process is managed by ``systemctl``, such as those created using the MinIO :ref:`DEB/RPM packages <deploy-minio-distributed-baremetal>`.
This procedure assumes you have the :envvar:`MINIO_CONFIG_ENV_FILE` variable set on all MinIO nodes.
1. Update the MinIO Binary on Each Node
.. include:: /includes/linux/common-installation.rst
:start-after: start-upgrade-minio-binary-desc
:end-before: end-upgrade-minio-binary-desc
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 binary version.
2. Restart the Deployment
Run the :mc-cmd:`mc admin service restart` command to restart all MinIO server processes in the deployment simultaneously.
The restart process typically completes within a few seconds and is *non-disruptive* to ongoing operations.
.. code-block:: shell
:class: copyable
@ -82,6 +85,8 @@ Use these steps to upgrade a MinIO deployment where the MinIO server process is
Replace :ref:`alias <alias>` of the MinIO deployment 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:`mc admin info` command to check that all MinIO servers are online, operational, and reflect the installed MinIO version.
@ -150,7 +155,7 @@ The command overwrites the existing ``minio`` binary at that path.
wget https://dl.min.io/server/minio/release/linux-amd64/minio
chmod +x ./minio
sudo mv -f ./minio /usr/local/bin/
sudo mv -f ./minio /usr/local/bin/minio
Once you have replaced the binary on all MinIO hosts in the deployment, you must restart all nodes simultaneously.