minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-31 18:04:52 +03:00
Code Activity

Correct mc admin user example, fix warnings (#969)

Browse Source 
A few small things:

* find/replace error from https://github.com/minio/docs/pull/950
* build warnings

Thank you @bendem!
https://github.com/minio/docs/pull/950#discussion_r1303044374
This commit is contained in:
Andrea Longo
2023-08-23 16:04:32 -06:00
committed by GitHub
parent 2908b2f9ee
commit 756d9f1799
6 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -171,7 +171,7 @@ Starting with :minio-release:`RELEASE.2023-05-27T05-56-19Z`, decommissioning ign
This avoids creating empty metadata on the remaining server pool(s) for objects that are effectively fully deleted.
Starting with :minio-release:`RELEASE.2023-06-23T20-26-00Z`, decommissioning also ignores object versions which have expired based on the configured :ref:`lifecycle rules <minio-lifecycle-management-expiration>` for the parent bucket.
Starting with :minio-release:`RELEASE.2023-06-29T05-12-28Z`, you can monitor ignored delete markers and expired objects during the decommission process with :mc:`mc admin trace --call decommission <mc admin trace --call>`.
Starting with :minio-release:`RELEASE.2023-06-29T05-12-28Z`, you can monitor ignored delete markers and expired objects during the decommission process with :mc-cmd:`mc admin trace --call decommission <mc admin trace --call>`.
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.