Oplog and replication mechanism in MongoDB

Introduction

The oplog helps keep copies of data in sync across multiple MongoDB servers. It records changes so all copies stay updated.

You want to keep a backup server updated automatically.

You need to share data across different locations for faster access.

You want to avoid losing data if one server fails.

You want to scale reads by having multiple copies of data.

You want to track changes made to your database over time.

Syntax

MongoDB

No direct query syntax; oplog is a special collection named 'oplog.rs' in the local database used internally by MongoDB replication.

The oplog is a capped collection that stores a rolling log of all operations that modify the data.

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

Examples

This command shows the last 5 operations recorded in the oplog.

MongoDB

use local
 db.getCollection('oplog.rs').find().limit(5).sort({$natural:-1})

Shows the status of the replica set, including which server is primary and which are secondaries.

MongoDB

rs.status()

Starts a new replica set to enable replication.

MongoDB

rs.initiate()

Sample Program

This sequence starts a replica set, checks its status, and shows the last 3 operations in the oplog.

MongoDB

rs.initiate()
rs.status()
use local
db.getCollection('oplog.rs').find().limit(3).sort({$natural:-1})

Important Notes

The oplog is only accessible on replica set members, not standalone servers.

Oplog entries include the operation type: insert (i), update (u), delete (d), etc.

Replication ensures data is copied from the primary to secondaries by replaying oplog entries.

Summary

The oplog is a special log that records all data changes in MongoDB replica sets.

Replication uses the oplog to keep multiple servers' data in sync automatically.

This helps with data safety, scaling, and availability.

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