[SERVER-34989] Secondary reads before the last-applied timestamp is set should take the PBWM lock and read at a timestamp Created: 14/May/18  Updated: 06/Dec/22  Resolved: 30/Apr/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 3.7.9
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

When a local snapshot is not available because the last-applied timestamp is not yet set, we default to reading without a timestamp, and without the PBWM lock.

Note that this is not necessarily a problem at the moment. If no last-applied timestamp is set, there are no replicated collections to read from, so a read wouldn't even be possible in this period.



 Comments   
Comment by Louis Williams [ 30/Apr/20 ]

This ticket does not describe a bug. I don't believe we want more dependencies on the PBWM lock, so I am closing this ticket.

Generated at Thu Feb 08 04:38:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.