Skip to content

Commit 7e9dbab

Browse files
Update content/integrate/redis-data-integration/data-pipelines/prepare-dbs/mongodb.md
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
1 parent 2fac14f commit 7e9dbab

File tree

1 file changed

+2
-1
lines changed
  • content/integrate/redis-data-integration/data-pipelines/prepare-dbs

1 file changed

+2
-1
lines changed

content/integrate/redis-data-integration/data-pipelines/prepare-dbs/mongodb.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,8 @@ The following table summarizes the steps to prepare a MongoDB database for RDI.
3838
| MongoDB Atlas | **[SSL required](https://debezium.io/documentation/reference/stable/connectors/mongodb.html#mongodb-property-mongodb-ssl-enabled)**, provide root CA as `SOURCE_DB_CACERT` secret in RDI |
3939
| Network | RDI Collector must reach all MongoDB nodes on required ports |
4040

41-
## 1. Configure Oplog Size
41+
## 1. Configure oplog size
42+
4243
The Debezium MongoDB connector relies on the [oplog](https://www.mongodb.com/docs/manual/core/replica-set-oplog/) to capture changes from a replica set. The oplog is a fixed-size, capped collection. When it reaches its maximum size, it overwrites the oldest entries. If the connector is stopped and restarted, it attempts to resume from its last recorded position in the oplog. If that position has been overwritten, the connector may fail to start and report an invalid resume token error.
4344

4445
To prevent this, ensure the oplog retains enough history for Debezium to resume streaming after interruptions. You can do this by:

0 commit comments

Comments
 (0)