Drop the dead MongoDB oplog-tailing code from mongoclient - #2684
Draft
delthas wants to merge 3 commits into
Draft
Conversation
Contributor
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Contributor
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
delthas
force-pushed
the
improvement/ARSN-622/drop-mongoclient-oplog-consumer
branch
from
August 7, 2026 13:46
a45c050 to
390c616
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## development/8.5 #2684 +/- ##
===================================================
- Coverage 74.73% 74.59% -0.14%
===================================================
Files 229 227 -2
Lines 18695 18567 -128
Branches 3894 3842 -52
===================================================
- Hits 13971 13850 -121
+ Misses 4719 4712 -7
Partials 5 5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
The mongoclient LogConsumer (and its ListRecordStream) tailed MongoDB's internal replica-set oplog (local.oplog.rs). It has been broken on MongoDB >= 7.1 since the oplog "h" field it uses as a cursor was removed (see ARSN-545), and its only consumer, backbeat's MongoLogReader (logSource "mongo"), was removed in BB-836. MongoReadStream (readStream.js) remains: it is used by MongoClientInterface for listings and is unrelated to the oplog. Issue: ARSN-622
delthas
force-pushed
the
improvement/ARSN-622/drop-mongoclient-oplog-consumer
branch
from
August 7, 2026 13:54
390c616 to
a309450
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The mongoclient
LogConsumer(and itsListRecordStream) tailed MongoDB's internal replica-set oplog (local.oplog.rs). It has been broken on MongoDB >= 7.1 since the oploghfield it uses as a cursor was removed — ARSN-545, closed Won't Fix — and its only consumer org-wide, backbeat'sMongoLogReader(logSource: "mongo"), was removed in BB-836 (scality/backbeat#2795).Changes:
lib/storage/metadata/mongoclient/LogConsumer.jsandListRecordStream.js, their unit tests, and theLogConsumerexport from themongoclientblock inindex.ts.MongoReadStream(readStream.js) remains — used byMongoClientInterfacefor listings, unrelated to the oplog. The bucketclientLogConsumer(raft log) is untouched.To land after scality/backbeat#2795 merges. Backbeat branches < 9.5 still reference this export but pin arsenal by commit, so they are unaffected until an arsenal bump.
Issue: ARSN-622