Choosing a good shard key in MongoDB

Introduction

Choosing a good shard key helps spread data evenly across servers. This makes your database faster and more reliable.

When your database grows too big for one server.

When you want to make queries faster by splitting data.

When you want to add more servers to handle more users.

When you want to avoid one server getting too busy.

When you want to keep data balanced and easy to find.

Syntax

MongoDB

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

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

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

Examples

This uses the orderId field as the shard key to split orders.

MongoDB

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

This uses userId to distribute user profiles across shards.

MongoDB

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

This shards data by time, useful for time-based queries.

MongoDB

sh.shardCollection("logs.events", { timestamp: 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 good shard key has many different values to spread data well.

Avoid shard keys that have the same value for many documents, or data will be uneven.

Think about your most common queries when choosing the shard key.

Summary

Shard keys split data to improve speed and balance.

Choose a shard key with many unique values.

Pick a shard key that matches how you search your data.

Practice

1. Which of the following is the most important characteristic of a good shard key in MongoDB?

easy

A. It is the smallest field in the document.

B. It is always a string type.

C. It has many unique values to distribute data evenly.

D. It contains only numeric values.

Solution

1. Step 1: Understand shard key purpose

   A shard key is used to split data across servers to balance load and improve speed.

2. Step 2: Identify key characteristic for even distribution

   A good shard key has many unique values to avoid data being stored unevenly on shards.

3. Final Answer:

   It has many unique values to distribute data evenly. -> Option C

4. Quick Check:

   Unique values = balanced shards [OK]

Hint: Choose shard keys with many unique values for balance [OK]

Common Mistakes:

• Thinking shard key must be string
• Choosing small fields regardless of uniqueness
• Assuming numeric only keys are best

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')

B. db.shardCollection('users', { userId: 1 })

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

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

Solution

1. Step 1: Recall syntax for sharding a collection

   The correct command is sh.shardCollection(namespace, shardKey), where namespace is 'database.collection'.

2. Step 2: Match options to syntax

   sh.shardCollection('mydb.users', { userId: 1 }) uses full namespace 'mydb.users' and correct shard key object { userId: 1 }.

3. Final Answer:

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

4. Quick Check:

   Full namespace + shard key object = correct syntax [OK]

Hint: Use full 'db.collection' name and shard key object [OK]

Common Mistakes:

• Using db.shardCollection instead of sh.shardCollection
• Passing shard key as string instead of object
• Omitting database name in namespace

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

medium

A. db.users.find({ age: { $gt: 30 } })

B. db.users.find({ country: 'USA' })

C. db.users.find({ name: 'Alice' })

D. db.users.find({ city: 'New York' })

Solution

1. Step 1: Understand shard key usage in queries

   Queries that include the shard key field can target specific shards, improving speed.

2. Step 2: Identify query with shard key field

   Only db.users.find({ country: 'USA' }) filters by country, the shard key, so it benefits most.

3. Final Answer:

   db.users.find({ country: 'USA' }) -> Option B

4. Quick Check:

   Query includes shard key field = faster query [OK]

Hint: Queries with shard key filter run faster [OK]

Common Mistakes:

• Assuming any query runs faster on sharded collection
• Ignoring shard key field in query
• Confusing shard key with indexed fields

4. You created a shard key on { userId: 1 } but notice all data is stored on one shard. What is the likely cause?

medium

A. The userId field has low cardinality (few unique values).

B. The shard key was created with descending order { userId: -1 }.

C. The collection is not sharded yet.

D. The shard key field is missing in some documents.

Solution

1. Step 1: Understand shard key distribution

   If the shard key has few unique values, data will cluster on few shards causing imbalance.

2. Step 2: Analyze options

   Low cardinality of userId causes data to be stored on one shard, matching the problem.

3. Final Answer:

   The userId field has low cardinality (few unique values). -> Option A

4. Quick Check:

   Low uniqueness = data imbalance [OK]

Hint: Low unique shard key values cause data to cluster [OK]

Common Mistakes:

• Thinking shard key order affects distribution
• Assuming collection is not sharded without checking
• Ignoring missing shard key fields in documents

5. You have a large collection of orders with fields orderId, customerId, and orderDate. You want to shard to optimize queries filtering by customerId and range queries on orderDate. Which shard key is best?

hard

A. { customerId: 1, orderDate: 1 }

B. { orderDate: 1 }

C. { orderId: 1 }

D. { customerId: 1 }

Solution

1. Step 1: Identify query patterns

   Queries filter by customerId and also use range on orderDate.

2. Step 2: Choose shard key matching query patterns

   A compound shard key with { customerId: 1, orderDate: 1 } supports both equality and range queries efficiently.

3. Final Answer:

   { customerId: 1, orderDate: 1 } -> Option A

4. Quick Check:

   Compound shard key matches query filters [OK]

Hint: Use compound shard key for multiple query filters [OK]

Common Mistakes:

• Choosing single field shard key ignoring query patterns
• Using orderId which is not queried
• Not using compound keys for combined filters