Read preference for replica sets in MongoDB - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a read preference in MongoDB replica sets?

A read preference tells MongoDB which members of a replica set to read data from. It helps balance load and control data freshness.

beginner

Name the five standard read preference modes in MongoDB.

Primary, PrimaryPreferred, Secondary, SecondaryPreferred, and Nearest.

beginner

What does the 'Primary' read preference mode do?

It directs all read operations to the primary member of the replica set, ensuring the most up-to-date data but no load balancing.

intermediate

How does 'SecondaryPreferred' read preference work?

It reads from secondary members if available, but falls back to primary if no secondary is reachable, balancing freshness and availability.

intermediate

Why might you use the 'Nearest' read preference mode?

To read from the member with the lowest network latency, regardless of whether it is primary or secondary, improving read speed.

Which read preference mode always reads from the primary member?

A SecondaryPreferred

B Secondary

C Primary

D Nearest

The 'Primary' mode directs all reads to the primary member only.

If you want to read from a secondary but fall back to primary if no secondary is available, which mode do you choose?

A Primary

B PrimaryPreferred

C Nearest

D SecondaryPreferred

'SecondaryPreferred' reads from secondaries first, then primary if needed.

What does the 'Nearest' read preference mode prioritize?

A Member with lowest network latency

B Primary member only

C Secondary members only

D Random member

'Nearest' reads from the member with the lowest network latency.

Which read preference mode can help distribute read load across secondaries?

A Secondary

B PrimaryPreferred

C Primary

D Nearest

'Secondary' mode reads only from secondary members, helping distribute load.

What happens if you use 'PrimaryPreferred' and the primary is down?

A Reads fail immediately

B Reads go to secondaries

C Reads go to nearest member

D Reads go to arbiter

'PrimaryPreferred' reads from primary if available, else from secondaries.

Explain the purpose of read preferences in MongoDB replica sets and list the available modes.

Think about balancing data freshness and load distribution.

Describe a scenario where using 'SecondaryPreferred' read preference is beneficial.

Consider read load and data freshness trade-offs.

Practice

1. What does the readPreference setting control in a MongoDB replica set?

easy

A. The size of the replica set

B. Which member to write data to

C. How often data is backed up

D. Which replica set member to read data from

Solution

1. Step 1: Understand the role of readPreference

   The readPreference setting tells MongoDB which replica set member to use for read operations.

2. Step 2: Differentiate read and write roles

   Writes always go to the primary, but reads can be directed to primary or secondary members based on readPreference.

3. Final Answer:

   Which replica set member to read data from -> Option D

4. Quick Check:

   Read preference = controls read source [OK]

Hint: Read preference decides read source, not write or backup [OK]

Common Mistakes:

• Confusing readPreference with write concern
• Thinking it controls backups
• Assuming it changes replica set size

2. Which of the following is the correct syntax to set read preference to secondaryPreferred in a MongoDB connection string?

easy

A. mongodb://host1,host2/?readPreference=secondaryPreferred

B. mongodb://host1,host2/?readPreference=primaryOnly

C. mongodb://host1,host2/?readPref=secondaryPreferred

D. mongodb://host1,host2/?readPreference=secondaryOnly

Solution

1. Step 1: Identify correct parameter name

   The correct parameter to set read preference in the connection string is readPreference.

2. Step 2: Match correct value

   secondaryPreferred is a valid read preference mode; others like primaryOnly or secondaryOnly are invalid or incorrect.

3. Final Answer:

   mongodb://host1,host2/?readPreference=secondaryPreferred -> Option A

4. Quick Check:

   Use readPreference with valid mode [OK]

Hint: Use exact parameter name 'readPreference' and valid mode [OK]

Common Mistakes:

• Using 'readPref' instead of 'readPreference'
• Using invalid modes like 'primaryOnly'
• Misspelling 'secondaryPreferred'

3. Given the following MongoDB query with read preference set to secondary:

db.collection.find({ status: "active" }).readPref("secondary")

What will happen if all secondary members are down?

medium

A. The query will read from the primary member

B. The query will fail with an error

C. The query will wait until a secondary is available

D. The query will return empty results

Solution

1. Step 1: Understand 'secondary' read preference behavior

   When read preference is set to secondary, reads must come from secondary members only.

2. Step 2: Consider all secondaries down scenario

   If no secondary is available, the query cannot read from primary or fallback; it results in an error.

3. Final Answer:

   The query will fail with an error -> Option B

4. Quick Check:

   Strict 'secondary' fails if no secondary [OK]

Hint: Strict 'secondary' read fails if no secondary available [OK]

Common Mistakes:

• Assuming fallback to primary happens automatically
• Thinking query waits indefinitely
• Expecting empty results instead of error

4. You wrote this code to read from a secondary member:

db.collection.find().readPref('secondaryPreferred')

But it still reads from the primary. What is the likely cause?

medium

A. The query must specify a filter to use read preference

B. The syntax for setting read preference is incorrect

C. No secondary members are available, so it falls back to primary

D. Read preference only works for writes

Solution

1. Step 1: Understand 'secondaryPreferred' behavior

   This mode reads from secondary if available; otherwise, it falls back to primary.

2. Step 2: Reason why primary is used

   If no secondary is available or reachable, the driver reads from primary as fallback.

3. Final Answer:

   No secondary members are available, so it falls back to primary -> Option C

4. Quick Check:

   'secondaryPreferred' falls back to primary if no secondary [OK]

Hint: 'secondaryPreferred' falls back to primary if no secondary [OK]

Common Mistakes:

• Thinking syntax is wrong when it is correct
• Believing read preference needs a filter
• Confusing read preference with write behavior

5. You want to optimize read performance by reading from secondaries but ensure data is fresh enough. Which read preference mode should you choose?

hard

A. secondaryPreferred

B. nearest

C. primary

D. secondary

Solution

1. Step 1: Understand read preference modes

   primary reads only from primary (fresh but may be slower), secondary reads only from secondaries (may be stale), secondaryPreferred reads secondaries or falls back to primary, nearest reads from the closest member regardless of type.

2. Step 2: Balance freshness and performance

   secondaryPreferred prefers secondaries for read performance optimization but falls back to the primary to ensure data freshness and availability.

3. Final Answer:

   secondaryPreferred -> Option A

4. Quick Check:

   secondaryPreferred prefers secondary perf + primary freshness fallback [OK]

Hint: 'secondaryPreferred' for secondary perf with primary fallback [OK]

Common Mistakes:

• Choosing 'secondary' which may return stale data
• Choosing 'primary' which may be slower
• Confusing 'secondaryPreferred' with 'nearest'