[SERVER-46287] Switch background validation to use read-at-time rather than a checkpoint cursor Created: 20/Feb/20 Updated: 29/Oct/23 Resolved: 06/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc0, 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Andrew Chen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||||||||||||||
| Sprint: | Execution Team 2020-03-09 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 26 | ||||||||||||||||||||||||||||
| Description |
|
Checkpoint cursors will no longer work due to the way fuzzy checkpoints work. However, with durable history, using a point-in-time read for background validation should have no issues. Therefore, we will switch to using point-in-time reads for background validation prior to the incorporation of the fuzzy checkpoint WT feature. |
| Comments |
| Comment by Githook User [ 06/Mar/20 ] |
|
Author: {'name': 'Andrew Chen', 'email': 'andrew.chen@10gen.com'}Message: delete mode 100644 jstests/noPassthrough/background_validation_checkpoint_existence.js (cherry picked from commit a2d5d3a4b48783913d7e8d0620c3e5dac8b85068) delete mode 100644 jstests/noPassthrough/background_validation_checkpoint_existence.js |
| Comment by Githook User [ 06/Mar/20 ] |
|
Author: {'name': 'Andrew Chen', 'email': 'andrew.chen@10gen.com'}Message: delete mode 100644 jstests/noPassthrough/background_validation_checkpoint_existence.js |