Docs Menu

Docs HomeDevelop ApplicationsMongoDB Manual

Change the Size of the Oplog

On this page

  • A. Connect to the replica set member
  • B. (Optional) Verify the current size of the oplog
  • C. Change the oplog size of the replica set member
  • D. (Optional) Compact to reclaim disk space


In MongoDB versions 3.4 and earlier, the oplog was resized by dropping and recreating the collection.

In MongoDB versions 3.6 and later, use the replSetResizeOplog command to resize the oplog as shown in this tutorial.

Starting in MongoDB 4.0, MongoDB forbids dropping the collection. For more information on this restriction, see Oplog Collection Behavior.

This procedure changes the size of the oplog [1] on each member of a replica set using the replSetResizeOplog command, starting with the secondary members before proceeding to the primary.

Perform these steps on each secondary replica set member first. Once you have changed the oplog size for all secondary members, perform these steps on the primary.

Connect to the replica set member using the mongo shell:

mongo --host <hostname>:<port>


If the replica set enforces authentication, you must authenticate as a user with privileges to modify the local database, such as the clusterManager or clusterAdmin role.

To view the current size of the oplog, switch to the local database and run db.collection.stats() against the collection. stats() displays the oplog size as maxSize.

use local

The maxSize field displays the collection size in bytes.

To resize the oplog, run the replSetResizeOplog command, passing the desired size in megabytes as the size parameter. The specified size must be greater than 990, or 990 megabytes.

The following operation changes the oplog size of the replica set member to 16 gigabytes, or 16000 megabytes.

db.adminCommand({replSetResizeOplog: 1, size: 16000})
[1] The oplog can grow past its configured size limit to avoid deleting the majority commit point.

Reducing the size of the oplog does not automatically reclaim the disk space allocated to the original oplog size. You must run compact against the collection in the local database to reclaim disk space. There are no benefits to running compact on the collection after increasing the oplog size.


Starting in MongoDB v4.4, a replica set member can replicate oplog entries while the compact operation is ongoing. Previously, oplog replication would be paused during compaction. Because of this, it was recommended that oplog compaction only be performed during maintenance windows, where writes could be minimized or stopped. In MongoDB 4.4 and later, it is no longer necessary to limit compaction operations on the oplog to maintenance windows, as oplog replication can continue as normal during compaction.

Do not run compact against the primary replica set member. Connect a mongo shell directly to the primary (not the replica set) and run rs.stepDown(). If successful, the primary steps down. From the mongo shell, run the compact command on the now-secondary member.

The following operation runs the compact command against the collection:

use local
db.runCommand({ "compact" : "" })

If the disk space allocated to the original oplog size is not reclaimed, restart mongod and run the commands from step D again. Restarting mongod runs recalculations in WiredTiger that might allow compact to release more space to the OS.

For clusters enforcing authentication, authenticate as a user with the compact privilege action on the local database and the collection. For complete documentation on compact authentication requirements, see compact Required Privileges.

← Replica Set Maintenance Tutorials