COF-C02 · Question #103
A virtual warehouse is created using the following command: Create warehouse my_WH with warehouse_size = MEDIUM min_cluster_count = 1 max_cluster_count = 1 auto_suspend = 60 auto_resume = true; The…
The correct answer is C. Configure the warehouse to a multi-cluster warehouse. The warehouse is configured as a single-cluster warehouse (min_cluster_count=1, max_cluster_count=1). When utilization graphs show sustained high load and queuing across multiple days, the bottleneck is concurrency - more queries arriving than the single cluster can handle…
Question
A virtual warehouse is created using the following command:
Create warehouse my_WH with warehouse_size = MEDIUM min_cluster_count = 1 max_cluster_count = 1 auto_suspend = 60 auto_resume = true; The image below is a graphical representation of the warehouse utilization across two days. What action should be taken to address this situation?
Exhibit
Options
- AIncrease the warehouse size from Medium to 2XL.
- BIncrease the value for the parameter MAX_CONCURRENCY_LEVEL.
- CConfigure the warehouse to a multi-cluster warehouse.
- DLower the value of the parameter STATEMENT_QUEUED_TIMEOUT_IN_SECONDS.
How the community answered
(26 responses)- A12% (3)
- B8% (2)
- C77% (20)
- D4% (1)
Explanation
The warehouse is configured as a single-cluster warehouse (min_cluster_count=1, max_cluster_count=1). When utilization graphs show sustained high load and queuing across multiple days, the bottleneck is concurrency - more queries arriving than the single cluster can handle simultaneously. The correct fix is to enable multi-cluster warehousing by increasing max_cluster_count beyond 1. Upsizing to 2XL adds compute per query but doesn't help concurrency; MAX_CONCURRENCY_LEVEL and STATEMENT_QUEUED_TIMEOUT_IN_SECONDS are tuning parameters, not scaling solutions.
Topics
Community Discussion
No community discussion yet for this question.