Read preference for replica sets in MongoDB - Step-by-Step Execution

Concept Flow - Read preference for replica sets

Client issues read request

↓

Check read preference setting

↓

Primary

↓

Send read to chosen replica

↓

Receive data from replica

↓

Return data to client

The client decides which replica to read from based on the read preference, then sends the read request to that replica and returns the data.

Execution Sample

MongoDB

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

This query reads data from a secondary replica in the replica set.

Execution Table

Step	Read Preference	Replica Chosen	Action	Result
1	secondary	Secondary replica	Send read request	Read data from secondary
2	primary	Primary replica	Send read request	Read data from primary
3	primaryPreferred	Primary replica if available	Send read request	Read data from primary
4	primaryPreferred	Secondary replica if primary down	Send read request	Read data from secondary
5	secondaryPreferred	Secondary replica if available	Send read request	Read data from secondary
6	secondaryPreferred	Primary replica if no secondary	Send read request	Read data from primary
7	nearest	Replica with lowest latency	Send read request	Read data from nearest replica
8	-	-	-	Stop: Read completed and data returned

💡 Read completes after sending request to chosen replica and receiving data

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
readPreference	not set	secondary	primary	primaryPreferred	secondaryPreferred	nearest
replicaChosen	none	secondary	primary	primary	secondary	nearest
readResult	none	data from secondary	data from primary	data from primary or secondary	data from secondary or primary	data from nearest replica

Key Moments - 3 Insights

Why does 'primaryPreferred' sometimes read from secondary?

Because if the primary is down or unreachable, 'primaryPreferred' falls back to reading from a secondary, as shown in execution_table rows 3 and 4.

What happens if no secondary is available but read preference is 'secondaryPreferred'?

The read goes to the primary replica instead, as shown in execution_table row 6.

How does 'nearest' read preference decide which replica to read from?

'Nearest' chooses the replica with the lowest network latency, regardless of primary or secondary status, as shown in execution_table row 7.

Visual Quiz - 3 Questions

Look at the execution_table, which replica does 'secondaryPreferred' read from if a secondary is available?

A Primary replica

B Secondary replica

C Nearest replica

D No replica

💡 Hint

Check execution_table row 5 under 'Replica Chosen'

At which step does the read preference fall back to secondary if primary is down?

A Step 2

B Step 3

C Step 4

D Step 6

💡 Hint

Look at execution_table rows 3 and 4 for 'primaryPreferred' behavior

If the read preference is 'nearest', which replica is chosen?

A Replica with lowest latency

B Secondary replica only

C Primary replica only

D Random replica

💡 Hint

See execution_table row 7 for 'nearest' read preference

Concept Snapshot

Read preference controls which replica in a MongoDB replica set handles read queries.
Options include primary, secondary, primaryPreferred, secondaryPreferred, and nearest.
The client sends reads to the chosen replica based on preference and availability.
Fallbacks occur if preferred replicas are unavailable.
This helps balance load and improve read scalability.

Full Transcript

This visual execution trace shows how MongoDB clients decide which replica to read from in a replica set based on the read preference setting. The client first checks the read preference, then selects the appropriate replica: primary, secondary, or nearest. For example, 'secondaryPreferred' reads from a secondary if available, otherwise falls back to primary. The execution table steps through each preference and the replica chosen, showing the read request sent and data returned. Variable tracking shows how the readPreference and replicaChosen change at each step. Key moments clarify common confusions like fallback behavior. The quiz tests understanding of which replica is chosen under different preferences. The snapshot summarizes the concept simply for quick review.