[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: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution NAMR Team 2023-08-21, Execution NAMR Team 2023-09-04 | ||||||||
| Participants: | |||||||||
| Description |
|
|
| Comments |
| Comment by Githook User [ 24/Aug/23 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |
| 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. |