alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DBZ-5812 Update common problems description re: snapshot initial mode

Browse Source
This commit is contained in:
Bob Roldan 2022-11-29 17:38:20 -05:00 committed by Jiri Pechanec
parent 980c4be471
commit dbdddc2485
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/modules/ROOT/pages/connectors/mongodb.adoc
View File

@ -1835,7 +1835,7 @@ The amount of time required for the connector to catch up depends upon the capab
However, if the connector remains stopped for a long enough interval, it can occur that MongoDB purges the oplog while the connector is inactive, so that the connector's last position is lost.
After the connector restarts, it cannot read the previous offset value to determine where to resume streaming.
Typically, if the connector's `snapshot.mode` property is set to the default value (`initial`), when it finds no offset in the data source, it runs a snapshot.
Typically, if the connector's `snapshot.mode` property is set to the default value (`initial`), when the connector does not find a value in its offsets topic, it runs a snapshot.
But in this situation, the connector detects stored offset values in its Kafka topic, but it cannot find a matching value in the database.
An error results and the connector fails.