-
Notifications
You must be signed in to change notification settings - Fork 16
REP-6804 Add option to read oplog directly #174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
(Still not review-ready because it has to store the selected change reader option then fail if it changes between invocations.) |
tdq45gj
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not familiar with the oplog tailing logic, but it looks good to me overall. I've left some small comments.
tdq45gj
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
This adds an opt-in mode to tail the oplog directly instead of reading a change stream. Oplog tailing is less resource-intensive on the server than a change stream, which yields better performance and allows verification of more migrations.
Oplog tailing carries a few caveats (or else it would be the default when possible):
Additional notes:
agglibrary, which simplifies aggregation usage in Go by providing types for various expressions.