[SERVER-48370] Make creating/extending backup cursors always persist most up-to-date size storer info Created: 21/May/20  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-49416 rollback_fuzzer_clean_shutdowns suite... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

As of SERVER-39593 and SERVER-48071, we persist the size storer when creating or extending a backup cursor, respectively. However, if there are concurrent writes, it is possible for this persisted size storer info to already be out of date by the time the backup cursor is actually created/extended.


Generated at Thu Feb 08 05:16:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.