Operational Defect Database
BugZero found this defect 54 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2623277
Consider sorting documents by recordId before applying entries on secondaries
Last update date:
3/26/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
Currently each applier thread receives a bunch of documents to insert (in the form of oplog entries). With recordIdsReplicated:true collections, the secondaries receive recordIds to use in the oplog entries, so they don't need to assign recordIds anymore. This means that the documents being inserted may not actually be in recordId order. SERVER-88392 tracks a dassert being triggered as a result. However, we should see if maybe we can sort the documents first by recordId to see if we can improve performance (making it different from the correctness issue in SERVER-88392).
Top User Comments
Steps to Reproduce
