Drop the unused "mongo" log source from the queue populator - #2795
Draft
delthas wants to merge 1 commit into
Draft
Drop the unused "mongo" log source from the queue populator#2795delthas wants to merge 1 commit into
delthas wants to merge 1 commit into
Conversation
Contributor
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Codecov Report❌ Patch coverage is
Additional details and impacted files
... and 1 file with indirect coverage changes
@@ Coverage Diff @@
## development/9.5 #2795 +/- ##
===================================================
+ Coverage 75.43% 75.70% +0.27%
===================================================
Files 201 200 -1
Lines 13935 13913 -22
===================================================
+ Hits 10512 10533 +21
+ Misses 3413 3370 -43
Partials 10 10
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Contributor
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
The "mongo" log source made the queue populator tail MongoDB's internal replica-set oplog (local.oplog.rs) through arsenal's mongoclient LogConsumer. It is broken on MongoDB >= 7.1 (the oplog "h" field used as a cursor was removed, see ARSN-545) and unused by every deployment, superseded by the oplog-populator + Kafka Connect architecture (logSource "kafka"). The queuePopulator.mongo configuration section remains: it is the shared MongoDB connection configuration used by the lifecycle bucket processor, notification queue processor, mongo processor and oplog populator. Issue: BB-836
delthas
force-pushed
the
improvement/BB-836/drop-mongo-log-source
branch
from
August 7, 2026 12:39
761a9e4 to
ddbe22a
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
"mongo"log source made the queue populator tail MongoDB's internal replica-set oplog (local.oplog.rs) through arsenal'smongoclient.LogConsumer. It is broken on MongoDB >= 7.1 (the oploghfield used as a cursor was removed — ARSN-545, closed Won't Fix) and unused by every deployment: Federation setsbucketd, and zenko-operator overrides itsmongofallback tokafkawhenever the oplog populator is enabled (the default on all mongo-backed deployments).Changes:
MongoLogReaderand itscase 'mongo'inQueuePopulator._setupLogSources(), plus related jsdoc and the log-source error message.'mongo'from thelogSourcejoi enum.LogReader._readLogOffset()— stored offsets are numeric for all remaining log sources.logSource: "mongo"to"kafka".The
queuePopulator.mongoconfig section is intentionally kept: it is the shared MongoDB connection configuration used by the lifecycle bucket processor, notification queue processor, mongo processor and oplog populator.Follow-ups tracked separately: removing
mongoclient/LogConsumer+ListRecordStreamfrom arsenal, and (optionally) thelogSource: "mongo"fallback in zenko-operator.Issue: BB-836