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

DOCS-867: MINIO Server Release.2023-05-27T05-56-19Z (#904)

Browse Source 
Partially addresses DOCS-898: MINIO Server RElease.2023-06-23T20-26-00Z
This commit is contained in:
Ravind Kumar
2023-06-29 16:50:46 -04:00
committed by GitHub
parent a6aa72c7d8
commit c45ac2b0f1
9 changed files with 141 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -167,6 +167,16 @@ nodes in the deployment at around the same time.
:start-after: start-nondisruptive-upgrade-desc
:end-before: end-nondisruptive-upgrade-desc
Decommissioning Ignores Expired Objects and Trailing ``DeleteMarker``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Starting with :minio-release:`RELEASE.2023-05-27T05-56-19Z`, decommissioning ignores objects where the only remaining version is a ``DeleteMarker``.
Starting with :minio-release:`minio-lifecycle-management-scanner`, decommissioning also ignores object versions which have expired based on the configured :ref:`lifecycle rules <minio-lifecycle-management-expiration>` for the parent bucket.
Once the decommissioning process completes, you can safely shut down that pool.
Since the only remaining data was scheduled for deletion *or* was only a ``DeleteMarker``, you can safely clear or destroy those drives as per your internal procedures.
Behavior
--------