Multi-cluster warehouses in Snowflake - Mini Project: Build & Apply

Multi-cluster Warehouses in Snowflake

📖 Scenario: You are managing a Snowflake data warehouse for a growing company. The company experiences varying query loads throughout the day. To handle this efficiently, you want to set up a multi-cluster warehouse that can automatically scale out and in based on demand.

🎯 Goal: Build a Snowflake multi-cluster warehouse configuration that starts with one cluster and can scale up to three clusters automatically when needed.

📋 What You'll Learn

Create a warehouse named analytics_wh with size MEDIUM

Enable multi-cluster warehouse (MULTI_CLUSTER = TRUE)

Set the minimum number of clusters to 1

Set the maximum number of clusters to 3

Enable auto-suspend after 10 minutes of inactivity

Enable auto-resume

💡 Why This Matters

🌍 Real World

Multi-cluster warehouses in Snowflake allow companies to handle fluctuating query loads by automatically scaling compute resources, ensuring fast query performance without manual intervention.

💼 Career

Cloud data engineers and analysts often configure multi-cluster warehouses to optimize cost and performance in Snowflake environments.

1

Create the initial warehouse

Create a warehouse named analytics_wh with size MEDIUM.

Snowflake

# Your code here to create the warehouse with name analytics_wh and size MEDIUM

Hint

Use the CREATE WAREHOUSE command with the WAREHOUSE_SIZE parameter.

2

Configure multi-cluster mode and cluster limits

Alter the warehouse analytics_wh to set MULTI_CLUSTER = TRUE, minimum clusters to 1, and maximum clusters to 3.

Snowflake

CREATE WAREHOUSE analytics_wh WITH WAREHOUSE_SIZE = 'MEDIUM';
-- Your code here to enable multi-cluster and cluster limits

Hint

Use ALTER WAREHOUSE to set MULTI_CLUSTER = TRUE, MIN_CLUSTER_COUNT, and MAX_CLUSTER_COUNT.

3

Enable auto-suspend and auto-resume

Alter the warehouse analytics_wh to enable AUTO_SUSPEND after 600 seconds (10 minutes) and enable AUTO_RESUME.

Snowflake

CREATE WAREHOUSE analytics_wh WITH WAREHOUSE_SIZE = 'MEDIUM';
ALTER WAREHOUSE analytics_wh SET MULTI_CLUSTER = TRUE, MIN_CLUSTER_COUNT = 1, MAX_CLUSTER_COUNT = 3;
-- Your code here to enable auto-suspend and auto-resume

Hint

Use ALTER WAREHOUSE to set AUTO_SUSPEND and AUTO_RESUME.

4

Complete the multi-cluster warehouse setup

Verify the full warehouse creation and configuration commands for analytics_wh include size MEDIUM, multi-cluster enabled (TRUE), minimum clusters 1, maximum clusters 3, auto-suspend after 600 seconds, and auto-resume enabled.

Snowflake

CREATE WAREHOUSE analytics_wh WITH WAREHOUSE_SIZE = 'MEDIUM';
ALTER WAREHOUSE analytics_wh SET MULTI_CLUSTER = TRUE, MIN_CLUSTER_COUNT = 1, MAX_CLUSTER_COUNT = 3;
ALTER WAREHOUSE analytics_wh SET AUTO_SUSPEND = 600, AUTO_RESUME = TRUE;
-- Your code here to finalize the warehouse configuration if needed

Hint

Review all previous commands to ensure the warehouse is fully configured.

Practice

1. What is the main purpose of a multi-cluster warehouse in Snowflake?

easy

A. To automatically add or remove compute clusters based on workload demand

B. To store data in multiple regions for disaster recovery

C. To encrypt data at rest and in transit

D. To create backups of data automatically every hour

Solution

1. Step 1: Understand multi-cluster warehouse functionality

   Multi-cluster warehouses adjust the number of compute clusters automatically to handle workload changes.

2. Step 2: Compare options with this functionality

   Only To automatically add or remove compute clusters based on workload demand describes automatic scaling of compute clusters based on demand.

3. Final Answer:

   To automatically add or remove compute clusters based on workload demand -> Option A

4. Quick Check:

   Multi-cluster warehouses scale clusters automatically = A [OK]

Hint: Remember: multi-cluster means auto scaling clusters [OK]

Common Mistakes:

• Confusing multi-cluster warehouses with data replication
• Thinking multi-cluster warehouses handle backups
• Assuming multi-cluster warehouses manage encryption

2. Which of the following is the correct way to set the minimum and maximum cluster count for a multi-cluster warehouse in Snowflake?

easy

A. ALTER WAREHOUSE mywh SET MIN_CLUSTER_COUNT = 2, MAX_CLUSTER_COUNT = 5;

B. ALTER WAREHOUSE mywh SET MIN_CLUSTERS = 2, MAX_CLUSTERS = 5;

C. ALTER WAREHOUSE mywh SET MIN_CLUSTER = 2, MAX_CLUSTER = 5;

D. ALTER WAREHOUSE mywh SET CLUSTER_MIN = 2, CLUSTER_MAX = 5;

Solution

1. Step 1: Recall correct parameter names for cluster count

   The correct parameters are MIN_CLUSTERS and MAX_CLUSTERS.

2. Step 2: Match syntax with correct parameters

   ALTER WAREHOUSE mywh SET MIN_CLUSTERS = 2, MAX_CLUSTERS = 5; uses the exact correct syntax and parameter names for Snowflake.

3. Final Answer:

   ALTER WAREHOUSE mywh SET MIN_CLUSTERS = 2, MAX_CLUSTERS = 5; -> Option B

4. Quick Check:

   Use MIN_CLUSTERS and MAX_CLUSTERS for scaling [OK]

Hint: Use full parameter names with _CLUSTERS suffix [OK]

Common Mistakes:

• Using incorrect parameter names like MIN_CLUSTER_COUNT
• Omitting the _CLUSTERS suffix
• Using wrong syntax for ALTER WAREHOUSE

3. Consider a multi-cluster warehouse configured with MIN_CLUSTER_COUNT=1 and MAX_CLUSTER_COUNT=3. If the workload suddenly increases, what will happen?

medium

A. The warehouse will reduce clusters to save cost

B. The warehouse will stay at 1 cluster and queue queries

C. The warehouse will shut down automatically

D. The warehouse will add clusters up to 3 to handle the workload

Solution

1. Step 1: Understand scaling behavior of multi-cluster warehouses

   When workload increases, Snowflake adds clusters up to the MAX_CLUSTER_COUNT to reduce query wait times.

2. Step 2: Apply configuration limits

   Since MAX_CLUSTER_COUNT is 3, the warehouse can scale from 1 up to 3 clusters automatically.

3. Final Answer:

   The warehouse will add clusters up to 3 to handle the workload -> Option D

4. Quick Check:

   Workload increase triggers cluster scaling up to max [OK]

Hint: Scaling adds clusters up to max limit on demand [OK]

Common Mistakes:

• Assuming clusters stay fixed at minimum count
• Thinking warehouse shuts down on high load
• Believing clusters reduce during high workload

4. You configured a multi-cluster warehouse with MIN_CLUSTER_COUNT=2 and MAX_CLUSTER_COUNT=4, but it never scales beyond 2 clusters even under heavy load. What is the most likely cause?

medium

A. The warehouse is paused

B. The MAX_CLUSTER_COUNT parameter is set incorrectly

C. The warehouse is set to SINGLE cluster mode instead of MULTI cluster mode

D. The warehouse size is too small to scale

Solution

1. Step 1: Check warehouse mode setting

   Multi-cluster scaling only works if the warehouse is in MULTI cluster mode, not SINGLE cluster mode.

2. Step 2: Understand effect of SINGLE cluster mode

   If set to SINGLE cluster mode, the warehouse will not scale beyond one cluster regardless of MIN or MAX settings.

3. Final Answer:

   The warehouse is set to SINGLE cluster mode instead of MULTI cluster mode -> Option C

4. Quick Check:

   Multi-cluster scaling requires MULTI cluster mode [OK]

Hint: Check warehouse mode: must be MULTI cluster for scaling [OK]

Common Mistakes:

• Ignoring warehouse mode and expecting scaling
• Assuming warehouse size limits scaling
• Not realizing paused warehouse cannot scale

5. You want to optimize a multi-cluster warehouse for unpredictable workloads that spike quickly but also have long idle periods. Which configuration is best to balance performance and cost?

hard

A. Set MIN_CLUSTER_COUNT=1 and MAX_CLUSTER_COUNT=5 with auto-suspend enabled

B. Set MIN_CLUSTER_COUNT=5 and MAX_CLUSTER_COUNT=5 with auto-suspend disabled

C. Set MIN_CLUSTER_COUNT=3 and MAX_CLUSTER_COUNT=3 with auto-suspend enabled

D. Set MIN_CLUSTER_COUNT=0 and MAX_CLUSTER_COUNT=1 with auto-suspend disabled

Solution

1. Step 1: Analyze workload characteristics

   Unpredictable spikes require ability to scale up quickly; long idle times require cost saving by suspending.

2. Step 2: Evaluate configuration options

   Set MIN_CLUSTER_COUNT=1 and MAX_CLUSTER_COUNT=5 with auto-suspend enabled allows scaling from 1 to 5 clusters and enables auto-suspend to save cost during idle periods.

3. Step 3: Compare other options

   Configurations with fixed cluster counts reduce flexibility; MIN_CLUSTER_COUNT=0 and MAX_CLUSTER_COUNT=1 with auto-suspend disabled limits max clusters and increases cost.

4. Final Answer:

   Set MIN_CLUSTER_COUNT=1 and MAX_CLUSTER_COUNT=5 with auto-suspend enabled -> Option A

5. Quick Check:

   Flexible scaling plus auto-suspend balances cost and performance [OK]

Hint: Use low min, high max clusters with auto-suspend for spikes [OK]

Common Mistakes:

• Fixing cluster count too high wastes cost
• Disabling auto-suspend wastes resources during idle
• Setting max clusters too low limits performance