From 1af11084ec699561f7a205f15b9323f2fb1e318b Mon Sep 17 00:00:00 2001 From: Daryl White <53910321+djwfyi@users.noreply.github.com> Date: Tue, 14 Nov 2023 15:35:20 -0500 Subject: [PATCH] Removing reference to unsupported decom with tiering (#1069) Per community Slack, correcting conflicting docs notes about decommissioning when tiering is enabled. Support for this was added in March 2023. --- .../install-deploy-manage/decommission-server-pool.rst | 8 -------- 1 file changed, 8 deletions(-) diff --git a/source/operations/install-deploy-manage/decommission-server-pool.rst b/source/operations/install-deploy-manage/decommission-server-pool.rst index 8857d817..03d1c031 100644 --- a/source/operations/install-deploy-manage/decommission-server-pool.rst +++ b/source/operations/install-deploy-manage/decommission-server-pool.rst @@ -120,14 +120,6 @@ 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 operations. -Decommissioning Does Not Support Tiering -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -MinIO does not support decommissioning pools in deployments with -:ref:`tiering ` configured. The MinIO -server rejects decommissioning attempts if any bucket in the deployment -has a tiering configuration. - Considerations --------------