From 2572c46cd052579b1a0fdb54b2c8bba153be08cb Mon Sep 17 00:00:00 2001 From: Andrea Longo Date: Thu, 20 Jul 2023 15:21:03 -0600 Subject: [PATCH] Decommissioning logs skipped delete markers and expired objects (#925) Add mention of logging skipped items Partially addresses https://github.com/minio/docs/issues/909 --- .../install-deploy-manage/decommission-server-pool.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/source/operations/install-deploy-manage/decommission-server-pool.rst b/source/operations/install-deploy-manage/decommission-server-pool.rst index caf436c0..20f7725c 100644 --- a/source/operations/install-deploy-manage/decommission-server-pool.rst +++ b/source/operations/install-deploy-manage/decommission-server-pool.rst @@ -170,7 +170,8 @@ 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``. This avoids creating empty metadata on the remaining server pool(s) for objects that are effectively fully deleted. -Starting with :minio-release:`minio-lifecycle-management-scanner`, decommissioning also ignores object versions which have expired based on the configured :ref:`lifecycle rules ` for the parent bucket. +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 ` 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 `. 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. @@ -187,7 +188,7 @@ If any objects return, MinIO returns an error that the decommission process fail If the decommission fails, customers should open a |SUBNET| issue for further assistance before retrying the decommission. Community users without a SUBNET subscription can retry the decommission process or seek additional support through the `MinIO Community Slack `__. -MinIO provides Community Support at best-effort only and provides no :abbr:`SLA ` around responsiveness. +MinIO provides Community Support at best-effort only and provides no :abbr:`SLA (Service Level Agreement)` around responsiveness. Decommissioning a Server with Tiering Enabled ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~