Write concern and data durability in MongoDB - Step-by-Step Execution

Concept Flow - Write concern and data durability

Client sends write request

↓

MongoDB receives write

↓

Apply write to primary

↓

Check write concern level

↓

w:0

↓

No ack

↓

Confirm durability

↓

Send response to client

This flow shows how MongoDB processes a write request and confirms it based on the write concern level, ensuring data durability as requested.

Execution Sample

MongoDB

db.collection.insertOne({name: "Alice"}, {writeConcern: {w: "majority"}})

Insert a document with write concern set to majority, waiting for confirmation from most nodes.

Execution Table

Step	Action	Write Concern Level	Result	Client Response
1	Client sends insertOne request	majority	Request received by primary	No response yet
2	Primary applies write	majority	Write applied on primary	No response yet
3	Primary waits for replicas	majority	Replicas apply write	No response yet
4	Majority of nodes confirm write	majority	Write durable on majority	Acknowledgement sent
5	Client receives acknowledgement	majority	Write confirmed durable	Success response

💡 Write concern majority met, client receives confirmation, execution ends.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
writeAppliedOnPrimary	false	true	true	true	true
writeAppliedOnReplicas	false	false	true	true	true
writeDurable	false	false	false	true	true
clientAcknowledged	false	false	false	true	true

Key Moments - 2 Insights

Why does the client not get a response immediately after the primary applies the write?

Because with write concern 'majority', MongoDB waits for most replicas to confirm the write before sending acknowledgement, as shown in execution_table step 3 and 4.

What happens if writeConcern is set to w:0?

The client gets no acknowledgement at all; the write is sent but the client does not wait for any confirmation, as indicated in the concept_flow branch for w:0.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the write become durable on the majority of nodes?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Check the 'Result' column for when 'Write durable on majority' occurs.

According to variable_tracker, when does clientAcknowledged change to true?

A After Step 5

B After Step 3

C After Step 4

D After Step 2

💡 Hint

Look at the 'clientAcknowledged' row and see when it becomes true.

If writeConcern was set to w:1, how would the client response timing change compared to w:majority?

A Client waits for all replicas

B Client gets acknowledgement after primary applies write

C Client never gets acknowledgement

D Client waits for no nodes

💡 Hint

Refer to concept_flow branches for different write concern levels.

Concept Snapshot

Write concern controls how MongoDB confirms writes.
'w:0' means no acknowledgement.
'w:1' waits for primary only.
'w:majority' waits for most nodes.
Higher write concern means better durability but slower response.

Full Transcript

This visual execution shows how MongoDB handles write concern and data durability. The client sends a write request with a specified write concern level. The primary node applies the write and, depending on the write concern, waits for replicas to confirm the write. For 'majority', the client only receives acknowledgement after most nodes confirm the write, ensuring durability. Variables track the write application and acknowledgement status step-by-step. Key moments clarify why acknowledgements are delayed and what happens with different write concern levels. Quizzes test understanding of when writes become durable and when clients get responses.