[SERVER-29491] Only full validate should verifyTable Created: 07/Jun/17 Updated: 30/Oct/23 Resolved: 26/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Geert Bosch | 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 | ||||||||||||||||
| Sprint: | Storage 2017-06-19, Storage 2017-07-10, Storage 2017-07-31 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
The verifyTable call will force a checkpoint and flush all in-memory data to disk and then verifies the on-disk data. Then after that, MongoDB will do its own scans to verify size and sort order. This requires reading all data twice from disk. We instead should always do the cheaper and more meaningful consistency checking, leaving the verifyTable for full : true cases. |
| Comments |
| Comment by Githook User [ 26/Jul/17 ] |
|
Author: {'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek', 'name': 'Gregory Wlodarek'}Message: |