
Explanation:
The question addresses queuing in a virtual warehouse, indicating that queries are waiting for resources. Based on Snowflake documentation and community consensus, the optimal solutions are: C) Change multi-cluster settings to add clusters, which dynamically scales compute to handle concurrent queries within the same warehouse, and D) Start a separate warehouse and move queued queries, which immediately offloads the queue to new compute. Both are valid per Snowflake's guidance for high load or queuing. Option A (decrease warehouse size) would worsen queuing by reducing capacity. Option B (decrease MIN_CLUSTER_COUNT) is irrelevant as it controls minimum clusters in multi-cluster warehouses but doesn't resolve active queuing. The community discussion shows support for both C and D, with upvoted comments citing Snowflake docs that recommend these actions for queuing scenarios.
Ultimate access to all questions.
If there is queuing in the virtual warehouse load monitoring chart, what actions should a Snowflake user take?
A
Decrease the warehouse size.
B
Decrease the MIN_CLUSTER_COUNT parameter.
C
Change the multi-cluster settings to add additional clusters.
D
Start a separate warehouse and move queued queries there.
No comments yet.