Oplog and replication mechanism in MongoDB - Step-by-Step Execution

Concept Flow - Oplog and replication mechanism

Primary Node receives write

↓

Primary writes change to Oplog

↓

Secondary nodes read Oplog entries

↓

Secondaries apply changes locally

↓

Secondaries update data to match Primary

↓

Clients read from Primary or Secondaries

The primary node records all data changes in the oplog. Secondary nodes read these changes and apply them to stay in sync.

Execution Sample

MongoDB

1. Primary inserts document
2. Primary writes insert to oplog
3. Secondary reads oplog entry
4. Secondary applies insert
5. Secondary data matches primary

Shows how a write on primary is recorded and replicated to secondaries via the oplog.

Execution Table

Step	Action	Oplog State	Secondary State	Result
1	Primary inserts document {name:'Alice'}	Empty	Empty	Primary data has Alice
2	Primary writes insert to oplog	Oplog: insert {name:'Alice'}	Empty	Oplog records insert
3	Secondary reads oplog entry	Oplog: insert {name:'Alice'}	Empty	Secondary sees insert
4	Secondary applies insert	Oplog: insert {name:'Alice'}	Data: {name:'Alice'}	Secondary data updated
5	Secondary data matches primary	Oplog: insert {name:'Alice'}	Data: {name:'Alice'}	Replication complete
6	No new oplog entries	Oplog: insert {name:'Alice'}	Data: {name:'Alice'}	Replication idle

💡 No new oplog entries to apply; secondaries are up to date

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
Primary Data	Empty	{name:'Alice'}	{name:'Alice'}	{name:'Alice'}
Oplog	Empty	insert {name:'Alice'}	insert {name:'Alice'}	insert {name:'Alice'}
Secondary Data	Empty	Empty	{name:'Alice'}	{name:'Alice'}

Key Moments - 2 Insights

Why does the secondary node read from the oplog instead of directly from the primary data?

The oplog records all changes in order, so secondaries can apply changes step-by-step to stay consistent. This is shown in execution_table rows 2 to 4.

What happens if the oplog is empty when the secondary tries to read?

If the oplog has no new entries (row 6), the secondary has no changes to apply and stays synchronized with the primary.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of the secondary data after step 3?

A Empty

B {name:'Alice'}

C Oplog entry present

D Primary data

💡 Hint

Check the 'Secondary State' column at step 3 in the execution_table

At which step does the secondary apply the insert operation?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look for the action 'Secondary applies insert' in the execution_table

If the primary writes a second insert to the oplog, what will happen next?

A Primary deletes old oplog entries

B Secondary ignores it

C Secondary reads and applies the new oplog entry

D Secondary resets data

💡 Hint

Replication mechanism means secondaries read all new oplog entries to stay updated

Concept Snapshot

MongoDB replication uses an oplog (operation log) on the primary.
Primary writes all data changes to the oplog.
Secondaries read oplog entries in order.
Secondaries apply these changes locally.
This keeps all nodes synchronized automatically.

Full Transcript

In MongoDB replication, the primary node records every data change in a special log called the oplog. This log keeps a list of all operations like inserts, updates, and deletes. Secondary nodes watch this oplog and read new entries as they appear. They then apply these changes to their own data copies. This process ensures that all secondary nodes stay in sync with the primary. The execution table shows step-by-step how a document inserted on the primary is recorded in the oplog and then replicated to a secondary. Variables track the state of data on primary, oplog contents, and secondary data after each step. Key moments clarify why secondaries read the oplog and what happens when no new changes exist. The quiz tests understanding of these steps and the replication flow. Overall, the oplog and replication mechanism provide a reliable way to keep multiple MongoDB nodes consistent.

Practice

1. What is the primary purpose of the oplog in MongoDB replica sets?

easy

A. To manage database indexes

B. To store user authentication details

C. To record all data changes for replication

D. To backup data to external storage

Solution

1. Step 1: Understand the role of oplog in MongoDB

   The oplog is a special log that records every data change in a replica set.

2. Step 2: Connect oplog to replication

   Replication uses the oplog to copy changes from the primary to secondary servers.

3. Final Answer:

   To record all data changes for replication -> Option C

4. Quick Check:

   Oplog records changes [OK]

Hint: Oplog logs changes for syncing replicas [OK]

Common Mistakes:

• Confusing oplog with user data storage
• Thinking oplog manages backups
• Assuming oplog stores indexes

2. Which of the following is the correct command to view the oplog entries in a MongoDB replica set?

easy

A. db.oplog.rs.find()

B. db.oplog.find()

C. db.replica.oplog()

D. db.oplogrs.find()

Solution

1. Step 1: Recall the oplog collection name

   The oplog is stored in the local database under the collection named oplog.rs.

2. Step 2: Identify the correct query syntax

   To view entries, use db.oplog.rs.find() in the mongo shell.

3. Final Answer:

   db.oplog.rs.find() -> Option A

4. Quick Check:

   Correct oplog collection query [OK]

Hint: Oplog collection is oplog.rs in local DB [OK]

Common Mistakes:

• Using wrong collection name like oplog or oplogrs
• Trying to call oplog as a function
• Missing the dot between oplog and rs

3. Given a MongoDB replica set, what will happen if the oplog on the primary server is deleted accidentally?

medium

A. Secondaries will stop replicating and may become stale

B. Secondaries will continue replicating normally

C. Primary will automatically recreate the oplog with old data

D. The replica set will elect a new primary immediately

Solution

1. Step 1: Understand oplog role in replication

   The oplog stores all changes that secondaries use to replicate data.

2. Step 2: Consequence of oplog deletion on primary

   If oplog is deleted, secondaries lose the source of changes and stop replicating, causing stale data.

3. Final Answer:

   Secondaries will stop replicating and may become stale -> Option A

4. Quick Check:

   Oplog missing = replication stops [OK]

Hint: No oplog means no replication updates [OK]

Common Mistakes:

• Assuming oplog auto-recreates with old data
• Thinking secondaries replicate without oplog
• Confusing oplog deletion with primary election

4. You run db.oplog.rs.find().limit(1) on a secondary node and get an error. What is the most likely cause?

medium

A. The oplog collection does not exist on secondaries

B. You need to switch to the local database first

C. The oplog is empty on secondaries

D. You must run the command on the primary node

Solution

1. Step 1: Check database context for oplog

   The oplog is stored in the local database, so you must switch to it before querying.

2. Step 2: Understand error cause

   If you run the command without use local, the shell looks in the wrong database and errors.

3. Final Answer:

   You need to switch to the local database first -> Option B

4. Quick Check:

   Oplog in local DB = switch DB first [OK]

Hint: Always use 'local' DB to query oplog [OK]

Common Mistakes:

• Trying to query oplog in wrong database
• Assuming oplog only exists on primary
• Thinking oplog is empty on secondaries

5. In a MongoDB replica set, how does the oplog help maintain data consistency during failover when the primary goes down?

hard

A. Oplog automatically merges conflicting writes from multiple primaries

B. Oplog backs up data externally to restore after failover

C. Oplog prevents any writes during failover to avoid conflicts

D. Secondaries use oplog entries to catch up and elect a new primary with latest data

Solution

1. Step 1: Understand failover in replica sets

   When primary fails, secondaries elect a new primary to continue operations.

2. Step 2: Role of oplog in failover

   Secondaries use oplog entries to apply all changes and ensure they have the latest data before election.

3. Step 3: Why other options are incorrect

   Oplog does not merge conflicting writes or prevent writes during failover; it also does not backup externally.

4. Final Answer:

   Secondaries use oplog entries to catch up and elect a new primary with latest data -> Option D

5. Quick Check:

   Oplog syncs data for failover [OK]

Hint: Oplog helps secondaries catch up before election [OK]

Common Mistakes:

• Thinking oplog merges conflicting writes
• Assuming oplog blocks writes during failover
• Confusing oplog with backup system