Write concern basics in MongoDB - Step-by-Step Execution

Concept Flow - Write concern basics

Client sends write request

↓

Write operation on primary

↓

Check write concern level

↓

w=1

↓

Acknowledge

↓

majority

↓

Send response

↓

Client receives

The client sends a write request, the primary node performs the write, then MongoDB checks the write concern level to decide how many nodes must confirm the write before responding to the client.

Execution Sample

MongoDB

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

Insert a document with write concern set to 'majority', waiting for most nodes to confirm the write.

Execution Table

Step	Action	Write Concern Level	Nodes Confirmed	Client Response
1	Client sends insertOne request	majority	0	Waiting
2	Primary writes document	majority	1 (primary)	Waiting
3	Secondary nodes replicate write	majority	2 (majority)	Waiting
4	Majority nodes confirmed write	majority	2 (majority)	Acknowledgement sent
5	Client receives acknowledgement	majority	2 (majority)	Write successful

💡 Write concern 'majority' satisfied when majority of nodes confirm the write, client receives success response.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
Nodes Confirmed	0	1 (primary)	2 (majority)	2 (majority)	2 (majority)
Client Response	Waiting	Waiting	Waiting	Acknowledgement sent	Write successful

Key Moments - 2 Insights

Why does the client wait before receiving a response?

Because the write concern 'majority' requires confirmation from most nodes, the client waits until enough nodes confirm the write (see execution_table step 3 and 4).

What happens if write concern is set to w:0?

The client does not wait for any acknowledgement and gets an immediate response, which means no confirmation of write success (not shown in this trace but implied in concept_flow).

Visual Quiz - 3 Questions

Look at the execution table, at which step does the client receive the acknowledgement?

A Step 2

B Step 4

C Step 5

D Step 3

💡 Hint

Check the action column in execution_table: step 5 says 'Client receives acknowledgement'.

According to variable_tracker, how many nodes have confirmed the write after step 3?

A 2

B 1

C 0

D 3

💡 Hint

Look at 'Nodes Confirmed' variable after Step 3 in variable_tracker.

If write concern was set to w:1, how would the client response timing change?

A Client would wait for majority nodes

B Client would get acknowledgement after primary writes

C Client would never get acknowledgement

D Client would wait for all nodes

💡 Hint

Refer to concept_flow where w=1 means acknowledgement after primary node writes.

Concept Snapshot

Write concern controls how many nodes must confirm a write before client gets response.
Common levels: w:0 (no ack), w:1 (primary ack), w:majority (most nodes ack).
Higher w means safer writes but slower response.
Set writeConcern in write operation options.
Client waits until required nodes confirm or timeout.
If not met, write error returned.

Full Transcript

Write concern in MongoDB defines how many nodes must confirm a write operation before the client receives a response. When a client sends a write request, the primary node writes the data. Depending on the write concern level, MongoDB waits for acknowledgements from other nodes. For example, with writeConcern 'majority', the client waits until most nodes confirm the write. This ensures data durability but can delay the response. If writeConcern is 'w:0', the client does not wait for any confirmation and gets an immediate response. The execution table shows the steps from sending the request, primary writing, secondaries replicating, to client receiving acknowledgement. The variable tracker shows how the number of nodes confirming the write increases over time. Understanding write concern helps balance between write safety and performance.