[SERVER-39593] Persist sizeStorer information before opening up backup cursor Created: 14/Feb/19 Updated: 29/Oct/23 Resolved: 01/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Storage NYC 2019-04-08 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
On normal clean shutdown, sizeStorer information will be persisted on disk. Therefore, the sizeStorer information will be accurate on restart. However, we didn't do that before opening up a backup cursor, so the sizeStorer information may be completely outdated. Even if we persist the sizeStorer information right before opening up backup cursor, there is still a window when more writes could go to disk (in the form of journal) and the sizeStorer information is outdated. So this improvement can only make the sizeStorer information more accurate but cannot guarantee 100% accurate unless we can stop writes in that window. |
| Comments |
| Comment by Githook User [ 02/Apr/19 ] |
|
Author: {'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: |
| Comment by Githook User [ 01/Apr/19 ] |
|
Author: {'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: |
| Comment by Githook User [ 01/Apr/19 ] |
|
Author: {'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: |