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.

Practice

1.

What does write concern in MongoDB control?

easy

A. The size of the database files

B. The speed of reading data from the database

C. The number of users connected to the database

D. How sure MongoDB is that your data is saved

Solution

1. Step 1: Understand the role of write concern

   Write concern defines the level of acknowledgment requested from MongoDB when writing data.

2. Step 2: Identify what write concern controls

   It controls how sure the database is that the data has been saved successfully.

3. Final Answer:

   How sure MongoDB is that your data is saved -> Option D

4. Quick Check:

   Write concern = Data save confirmation [OK]

Hint: Write concern = data save confirmation level [OK]

Common Mistakes:

• Confusing write concern with read speed
• Thinking it controls database size
• Assuming it manages user connections

2.

Which of the following is the correct way to set a write concern of w: 1 in a MongoDB insert operation?

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

easy

A. {w: 1}

B. {w: 'majority'}

C. {w: 0}

D. {w: true}

Solution

1. Step 1: Recall write concern syntax

   Write concern is set as an object with key w and a value indicating the level.

2. Step 2: Match the correct value for w: 1

   The correct syntax is {w: 1} to wait for acknowledgment from one server.

3. Final Answer:

   {w: 1} -> Option A

4. Quick Check:

   Write concern syntax = {w: 1} [OK]

Hint: Use {w: 1} to wait for one server acknowledgment [OK]

Common Mistakes:

• Using string 'true' instead of number 1
• Confusing 'majority' with numeric 1
• Setting w to 0 which means no acknowledgment

3.

What will happen if you run this MongoDB command?

db.orders.insertOne({item: 'book'}, {writeConcern: {w: 0}})

medium

A. The insert does not wait for any confirmation

B. The insert waits for confirmation from the server

C. The insert waits for confirmation from majority of servers

D. The insert throws a syntax error

Solution

1. Step 1: Understand writeConcern w: 0 meaning

   Setting w: 0 means no acknowledgment is required from the server.

2. Step 2: Predict behavior of insertOne with w: 0

   The insert operation will send data but not wait for any confirmation, so it returns immediately.

3. Final Answer:

   The insert does not wait for any confirmation -> Option A

4. Quick Check:

   w: 0 means no wait for confirmation [OK]

Hint: w: 0 means fire-and-forget, no wait [OK]

Common Mistakes:

• Thinking w: 0 waits for server confirmation
• Assuming syntax error due to w: 0
• Confusing w: 0 with majority write concern

4.

Identify the error in this MongoDB write concern usage:

db.users.insertOne({name: 'Bob'}, {writeConcern: {w: 'two'}})

medium

A. The write concern should be set as a string without quotes

B. The value 'two' is invalid for write concern w

C. The insertOne method does not accept write concern

D. The document format is incorrect

Solution

1. Step 1: Check valid values for write concern w

   Write concern w accepts numbers or 'majority', not arbitrary strings like 'two'.

2. Step 2: Identify the error in the given code

   Using 'two' is invalid and will cause an error.

3. Final Answer:

   The value 'two' is invalid for write concern w -> Option B

4. Quick Check:

   Write concern w must be number or 'majority' [OK]

Hint: Write concern w must be number or 'majority' only [OK]

Common Mistakes:

• Using invalid string values for w
• Thinking writeConcern is not allowed in insertOne
• Confusing quotes usage in write concern

5.

You want to ensure your MongoDB write operation waits for confirmation from the majority of replica set members but also times out if it takes more than 5 seconds. Which write concern option should you use?

hard

A. {w: 0, wtimeout: 5000}

B. {w: 1, wtimeout: 5000}

C. {w: 'majority', wtimeout: 5000}

D. {w: 'majority', wtimeout: 0}

Solution

1. Step 1: Understand write concern for majority

   To wait for majority confirmation, w must be set to 'majority'.

2. Step 2: Add timeout for waiting

   Use wtimeout to specify max wait time in milliseconds; 5000 means 5 seconds.

3. Step 3: Combine options correctly

   The correct option is {w: 'majority', wtimeout: 5000} to wait for majority with 5 seconds timeout.

4. Final Answer:

   {w: 'majority', wtimeout: 5000} -> Option C

5. Quick Check:

   Majority + 5s timeout = {w: 'majority', wtimeout: 5000} [OK]

Hint: Use w: 'majority' with wtimeout in ms for timeout [OK]

Common Mistakes:

• Using w: 1 instead of 'majority' for majority confirmation
• Setting wtimeout to 0 which means no timeout
• Using w: 0 which disables waiting