Skip to content

Commit 43a58d7

Browse files
authored
Add description of how automatical idling works with RMV and S3 Queue
1 parent d311f98 commit 43a58d7

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/en/cloud/manage/scaling.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,8 @@ In the **Settings** page, you can also choose whether or not to allow automatic
8686

8787
:::note
8888
In certain special cases, for instance when a service has a high number of parts, the service will not be idled automatically.
89+
90+
The service may enter an idle state where it suspends refreshes of [refreshable materialized views](/docs/en/materialized-view/refreshable-materialized-view), consumption from [S3Queue](/docs/en/engines/table-engines/integrations/s3queue), and scheduling of new merges. Existing merge operations will complete before the service transitions to the idle state. To ensure continuous operation of refreshable materialized views and S3Queue consumption, disable the idle state functionality.
8991
:::
9092

9193
:::danger When not to use automatic idling

0 commit comments

Comments
 (0)