mirror of
https://github.com/minio/docs.git
synced 2025-07-30 07:03:26 +03:00
Adding order of operations for expansion and decommission (#705)
- Modifies decommissioning page to mention completing any planned expansions first. - Modifies expand deployment page to mention completing before doing any planned decommssions. - Minor grammar fixes to expand tenant page. Closes #702
This commit is contained in:
@ -132,6 +132,18 @@ has a tiering configuration.
|
||||
Considerations
|
||||
--------------
|
||||
|
||||
Replacing a Server Pool
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
For hardware upgrade cycles where you replace old pool hardware with a new pool, you should :ref:`add the new pool through expansion <expand-minio-distributed>` before starting the decommissioning of the old pool.
|
||||
Adding the new pool first allows the decommission process to transfer objects in a balanced way across all available pools, both existing and new.
|
||||
|
||||
Complete any planned :ref:`hardware expansion <expand-minio-distributed>` prior to decommissioning older hardware pools.
|
||||
|
||||
Decommissioning requires that a cluster's topology remain stable throughout the pool draining process.
|
||||
Do **not** attempt to perform expansion and decommission changes in a single step.
|
||||
|
||||
|
||||
Decommissioning Ignores Delete Markers
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
@ -256,6 +256,8 @@ those appropriate for your deployment.
|
||||
Review the :ref:`expand-minio-distributed-prereqs` before starting this
|
||||
procedure.
|
||||
|
||||
Complete any planned hardware expansion prior to :ref:`decommissioning older hardware pools <minio-decommissioning>`.
|
||||
|
||||
1) Install the MinIO Binary on Each Node in the New Server Pool
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
@ -19,8 +19,8 @@ Prerequisites
|
||||
MinIO Kubernetes Operator and Plugin
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
This procedures on this page *requires* a valid installation of the MinIO Kubernetes Operator and assumes the local host has a matching installation of the MinIO Kubernetes Operator.
|
||||
This procedure assumes the latest stable Operator and Plugin version |operator-version-stable|.
|
||||
This procedure on this page *requires* a valid installation of the MinIO Kubernetes Operator and assumes the local host has a matching installation of the MinIO Kubernetes Operator.
|
||||
This procedure assumes the latest stable Operator and Plugin version, |operator-version-stable|.
|
||||
|
||||
See :ref:`deploy-operator-kubernetes` for complete documentation on deploying the MinIO Operator.
|
||||
|
||||
|
Reference in New Issue
Block a user