Shard key selection importance in MongoDB

Introduction

Choosing the right shard key helps your database split data evenly and find data quickly.

When you want to store lots of data across many servers.

When your app needs fast access to specific pieces of data.

When you want to avoid some servers getting too busy while others are idle.

When you plan to grow your database size over time.

When you want to keep your database reliable and fast.

Syntax

MongoDB

sh.shardCollection("database.collection", { shardKeyField: 1 })

The shard key is a field or fields used to split data across servers.

Use 1 for ascending order or -1 for descending order in the shard key.

Examples

This sets 'orderId' as the shard key to split the 'orders' collection.

MongoDB

sh.shardCollection("shop.orders", { orderId: 1 })

This uses a compound shard key with 'userId' and 'region' to distribute data.

MongoDB

sh.shardCollection("users.data", { userId: 1, region: 1 })

Sample Program

This example enables sharding on the 'shop' database and sets 'orderId' as the shard key for the 'orders' collection.

MongoDB

use shop
sh.enableSharding("shop")
sh.shardCollection("shop.orders", { orderId: 1 })

Important Notes

A bad shard key can cause uneven data distribution, making some servers overloaded.

Choose a shard key with many different values to spread data well.

Shard keys cannot be changed easily after setting, so choose carefully.

Summary

Shard keys decide how data is split across servers.

Good shard keys keep data balanced and queries fast.

Pick shard keys with many unique values and that match your query patterns.

Practice

1. Why is choosing a good shard key important in MongoDB?

easy

A. It reduces the number of collections.

B. It increases the size of each document.

C. It helps distribute data evenly across servers.

D. It makes the database schema simpler.

Solution

1. Step 1: Understand shard key role

   The shard key determines how data is split across multiple servers in a cluster.

2. Step 2: Importance of even distribution

   A good shard key ensures data is balanced, preventing some servers from being overloaded.

3. Final Answer:

   It helps distribute data evenly across servers. -> Option C

4. Quick Check:

   Shard key = data distribution [OK]

Hint: Shard key controls data spread, pick for balance [OK]

Common Mistakes:

• Thinking shard key changes document size
• Confusing shard key with schema design
• Believing shard key reduces collections

2. Which of the following is the correct syntax to create a sharded collection with shard key { userId: 1 } in MongoDB?

easy

A. sh.shardCollection('mydb.users', { userId: 1 })

B. sh.shardCollection('mydb.users', 'userId')

C. sh.shardCollection('mydb.users', { userId: 'asc' })

D. sh.shardCollection('mydb.users', ['userId'])

Solution

1. Step 1: Review shardCollection syntax

   The correct syntax requires the namespace string and a document specifying the shard key fields with direction (1 or -1).

2. Step 2: Match correct option

   sh.shardCollection('mydb.users', { userId: 1 }) uses the correct format: database.collection and shard key as document with 1.

3. Final Answer:

   sh.shardCollection('mydb.users', { userId: 1 }) -> Option A

4. Quick Check:

   shardCollection needs {field: 1} format [OK]

Hint: Shard key must be a document with field and 1 or -1 [OK]

Common Mistakes:

• Passing shard key as string instead of document
• Using array instead of document for shard key
• Using 'asc' instead of 1 for direction

3. Given a collection sharded on { orderId: 1 }, which query will benefit most from the shard key?

medium

A. db.orders.find({ customerName: 'Alice' })

B. db.orders.find({ total: { $gt: 100 } })

C. db.orders.find({ status: 'shipped' })

D. db.orders.find({ orderId: 12345 })

Solution

1. Step 1: Understand shard key query targeting

   Queries that include the shard key field can be routed directly to the relevant shard.

2. Step 2: Identify query with shard key

   Only the query filtering by orderId uses the shard key, so it benefits most.

3. Final Answer:

   db.orders.find({ orderId: 12345 }) -> Option D

4. Quick Check:

   Query with shard key = targeted query [OK]

Hint: Queries with shard key filter hit one shard fast [OK]

Common Mistakes:

• Assuming any query benefits from shard key
• Confusing shard key with indexed fields
• Ignoring shard key presence in query

4. You created a shard key on { country: 1 } but notice one shard stores 90% of data. What is the likely problem?

medium

A. The shard key syntax was incorrect.

B. The shard key has low cardinality causing data imbalance.

C. The collection is not sharded properly.

D. The shard key field is missing in documents.

Solution

1. Step 1: Analyze shard key cardinality

   Shard keys with few unique values (low cardinality) cause uneven data distribution.

2. Step 2: Identify cause of imbalance

   Country likely has few distinct values, so one shard holds most data.

3. Final Answer:

   The shard key has low cardinality causing data imbalance. -> Option B

4. Quick Check:

   Low cardinality shard key = data imbalance [OK]

Hint: Low unique shard keys cause uneven data spread [OK]

Common Mistakes:

• Blaming syntax without checking data
• Assuming collection is unsharded
• Ignoring shard key field presence

5. You want to shard a large user collection. Which shard key choice is best to keep data balanced and queries efficient?

hard

A. Use { userId: 1 } because it has many unique values and is in queries.

B. Use { country: 1 } because it groups users by location.

C. Use { signupDate: 1 } because dates are sequential.

D. Use { status: 1 } because it has few distinct values.

Solution

1. Step 1: Evaluate shard key uniqueness

   A good shard key has many unique values to distribute data evenly.

2. Step 2: Match shard key to query patterns

   UserId is unique and commonly used in queries, improving efficiency.

3. Step 3: Avoid low cardinality keys

   Country and status have few distinct values, causing imbalance; signupDate is sequential, causing chunk hotspots.

4. Final Answer:

   Use { userId: 1 } because it has many unique values and is in queries. -> Option A

5. Quick Check:

   High cardinality + query use = best shard key [OK]

Hint: Pick shard key with many unique values and query use [OK]

Common Mistakes:

• Choosing sequential or low cardinality fields
• Ignoring query patterns when selecting shard key
• Assuming grouping fields balance data well