Operational Defect Database
BugZero found this defect 24 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2654403
`modify` change events don’t reflect effective cappedSize
Last update date:
4/26/2024
Affected products:
MongoDB Server
Affected releases:
6.0.14
Fixed releases:
No fixed releases provided.
Description:
Info
If you run: {{collMod: "mycoll", cappedSize: 100000}} … while a DDL-aware change stream is running … > cs = db.getSiblingDB('admin').aggregate([{$changeStream: { showExpandedEvents: true, allChangesForCluster: true }}]) > cs.next() … you’ll see a change event with: options: { capped: true, size: 100000 } … even though the collection’s actual new limit, due to some rounding that seems to happen, is 100,096 documents. The change stream should indicate size: 100096 since that’s the actual change that occurred on the server. cc matt.kneiser@mongodb.com, from a Slack thread We do not see this in v7+.
Top User Comments
Steps to Reproduce
