[SERVER-79619] Re-evaluate SecondaryReadsDuringBatchApplicationAreAllowed unit test Created: 02/Aug/23  Updated: 29/Oct/23  Resolved: 24/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-79392 Remove ParallelBatchWriterMode class Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution NAMR Team 2023-08-21, Execution NAMR Team 2023-09-04
Participants:

 Description   

SERVER-79392 modifies this unit test now that Lock::ParallelBatchWriterMode is being removed, but with the PBWM gone we should re-evaluate what this test is doing and whether it is still valuable as currently written.



 Comments   
Comment by Githook User [ 24/Aug/23 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-79619 Remove `SecondaryReadsDuringBatchApplicationAreAllowed`
Branch: master
https://github.com/mongodb/mongo/commit/643fbf6508eea474302711bc58dea9595a205e5c

Comment by Gregory Noma [ 22/Aug/23 ]

Previously, this test was showing that despite oplog application holding the PBWM in exclusive mode, a secondary reader can still acquire its resources to perform a read. Now that the PBWM is gone, maybe we should just remove this test. Or maybe we should change it to instead show that it's not reading at a timestamp in the middle of the batch.

Generated at Thu Feb 08 06:41:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.