Operational Defect Database
BugZero found this defect 25 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2652240
Fix read_and_write_distribution.js that uses wrong secondary read after majority write assumption
Last update date:
4/24/2024
Affected products:
MongoDB Server
Affected releases:
8.0.0-rc0
Fixed releases:
No fixed releases provided.
Description:
Info
Due to PM-3489, there is no guarantee to see documents by running a secondary read after a write with majority. In `read_and_write_distribution.js`, analyze shard key is not finding any document, because the previous write is majority replicated (in the oplog) but not applied, so analyze shard key may fail with `CollectionIsEmptyLocally` before failing with the expected error. The goal of this ticket is to make that test not rely on the wrong assumption to see documents by the secondary read by analyze shard key after a majority write have inserted them.
Top User Comments
Steps to Reproduce
