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

Corrects minor issues noted in issue #492

Browse Source
This commit is contained in:
Daryl White
2022-06-27 18:34:38 -05:00
parent 1c416561ef
commit 1cef7df283
2 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
source/administration/identity-access-management/minio-identity-management.rst
View File

@ -35,7 +35,7 @@ user's authorized actions and resources *or* assign the user to :ref:`groups
:ref:`minio-access-management` for more information. :ref:`minio-access-management` for more information.
.. admonition:: External Identity Management .. admonition:: External Identity Management
:class: dropdown, note :class: note
MinIO supports external management of identities using either an MinIO supports external management of identities using either an
OpenID Connect (OIDC) or Active Directory/LDAP IDentity Provider (IDP). OpenID Connect (OIDC) or Active Directory/LDAP IDentity Provider (IDP).

18
source/operations/install-deploy-manage/decommission-server-pool.rst
View File

@ -11,7 +11,7 @@ Decommission a Server Pool
:depth: 1 :depth: 1
Starting with :minio-release:`RELEASE.2022-01-25T19-56-04Z`, MinIO supports Starting with :minio-release:`RELEASE.2022-01-25T19-56-04Z`, MinIO supports
decommissioning and removing a :ref:`server pools <minio-intro-server-pool>` decommissioning and removing a :ref:`server pool <minio-intro-server-pool>`
from a deployment. Decommissioning is designed for removing an older server pool from a deployment. Decommissioning is designed for removing an older server pool
whose hardware is no longer sufficient or performant compared to the pools in whose hardware is no longer sufficient or performant compared to the pools in
the deployment. MinIO automatically migrates data from the decommissioned pool the deployment. MinIO automatically migrates data from the decommissioned pool
@ -89,12 +89,13 @@ this procedure.
Deployment Must Have Sufficient Storage Deployment Must Have Sufficient Storage
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The decommissioning process migrates objects from the target pool to other The decommissioning process migrates objects from the target pool to other pools in the deployment.
pools in the deployment. The total available storage on the deployment The total available storage on the deployment *must* exceed the total storage of the decommissioned pool.
*must* exceed the total storage of the decommissioned pool.
For example, consider a deployment with the following distribution of Use the `Erasure Code Calculator <https://min.io/product/erasure-code-calculator>`__ to determine the usable storage capacity.
used and free storage: Then reduce that by the size of the objects already on the deployment.
For example, consider a deployment with the following distribution of used and free storage:
.. list-table:: .. list-table::
:stub-columns: 1 :stub-columns: 1
@ -113,9 +114,8 @@ used and free storage:
- 100TB Used - 100TB Used
- 200TB Total - 200TB Total
Decommissioning Pool 1 requires distributing the 100TB of used storage Decommissioning Pool 1 requires distributing the 100TB of used storage across the remaining pools.
across the remaining pools. Pool 2 and Pool 3 each have 100TB of unused Pool 2 and Pool 3 each have 100TB of unused storage space and can safely absorb the data stored on Pool 1.
storage space and can safely absorb the data stored on Pool 1.
However, if Pool 1 were full (e.g. 200TB of used space), decommissioning would However, if Pool 1 were full (e.g. 200TB of used space), decommissioning would
completely fill the remaining pools and potentially prevent any further write completely fill the remaining pools and potentially prevent any further write