[SERVER-85307] queryableBackupMode in sharded clusters fails to apply critical section related entries Created: 17/Jan/24 Updated: 06/Feb/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Paolo Polato |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Operating System: | ALL |
| Sprint: | CAR Team 2024-02-05, CAR Team 2024-02-19 |
| Participants: | |
| Story Points: | 2 |
| Description |
|
While setting up the queryableBackupMode we can set a time to apply all the oplogs from that time, this is being test today, however, with the work of PM-635 once we're on queryableBackupMode this checks are failing but they shouldn't, because if we're applying an oplog entry related to the critical section, we have to take the collection lock in the observer. |