[SERVER-57354] [v5.0] Disable background validation on capped collections in FCV 4.4 Created: 02/Jun/21 Updated: 29/Oct/23 Resolved: 02/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | 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: | Execution Team 2021-06-14 | ||||
| Participants: | |||||
| Linked BF Score: | 32 | ||||
| Description |
|
Capped collections perform un-timestamped writes to delete expired documents in FCV <= 4.4, but all documents will have had an assigned timestamp when first inserted. This breaks contracts with the storage engine regarding mixed-use timestamps and means that point-in-time reads do not work correctly on capped collections. As a result, background validation when reading documents that have just been deleted. |
| Comments |
| Comment by Githook User [ 02/Jun/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |