From 67545434896c4a62a154a33c1f01664419b25550 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ra=C3=BAl=20Mar=C3=ADn?= Date: Thu, 2 Jul 2026 10:22:26 +0200 Subject: [PATCH] Update 05_automatic_idling.md idle parts doesn't make sense, it should be active parts --- docs/cloud/features/04_automatic_scaling/05_automatic_idling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cloud/features/04_automatic_scaling/05_automatic_idling.md b/docs/cloud/features/04_automatic_scaling/05_automatic_idling.md index 57929489e6d..47f3acaf7cb 100644 --- a/docs/cloud/features/04_automatic_scaling/05_automatic_idling.md +++ b/docs/cloud/features/04_automatic_scaling/05_automatic_idling.md @@ -17,7 +17,7 @@ When you create a ClickHouse Cloud service, the default setting for the IP allow ### Adaptive Idling {#adaptive-idling} ClickHouse Cloud implements adaptive idling to prevent disruptions while optimizing cost savings. The system evaluates several conditions before transitioning a service to idle. Adaptive idling overrides the idling duration setting when any of the below listed conditions are met: -- When the number of parts exceeds the maximum idle parts threshold (default: 10,000), the service isn't idled so that background maintenance can continue +- When the number of parts exceeds the maximum active parts threshold (default: 10,000), the service isn't idled so that background maintenance can continue - When there are ongoing merge operations, the service isn't idled until those merges complete to avoid interrupting critical data consolidation - Additionally, the service also adapts idle timeouts based on server initialization time: - If server initialization time is less than 15 minutes, no adaptive timeout is applied and the customer-configured default idle timeout is used