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

[docs] Fixing broken link

Browse Source
This commit is contained in:
Gunnar Morling 2022-01-18 12:46:16 +01:00 committed by GitHub
parent 8fd3243a86
commit 7dc5e97041
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
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

@ -58,7 +58,7 @@ MongoDB replication works by having the primary record the changes in its _oplog
When a new server is added to a replica set, that server first performs an https://docs.mongodb.com/manual/core/replica-set-sync/[snapshot] of all of the databases and collections on the primary, and then reads the primary's oplog to apply all changes that might have been made since it began the snapshot. When a new server is added to a replica set, that server first performs an https://docs.mongodb.com/manual/core/replica-set-sync/[snapshot] of all of the databases and collections on the primary, and then reads the primary's oplog to apply all changes that might have been made since it began the snapshot.
This new server becomes a secondary (and able to handle queries) when it catches up to the tail of the primary's oplog. This new server becomes a secondary (and able to handle queries) when it catches up to the tail of the primary's oplog.
MongoDB connector supports two distinct modes of capturing the changes controlled by xref:mongodb-property-capture-mode[[`capture.mode`] option: MongoDB connector supports two distinct modes of capturing the changes controlled by the xref:mongodb-property-capture-mode[`capture.mode`] option:
* oplog based * oplog based
* change streams based * change streams based