[SERVER-62336] Tolerate SnapshotTooOld errors in dbCheck testing Created: 04/Jan/22 Updated: 29/Oct/23 Resolved: 20/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0, 5.0.6, 4.4.13 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Josef Ahmad | Assignee: | Josef Ahmad |
| 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 | ||||||||
| Backport Requested: |
v5.0, v4.4
|
||||||||
| Sprint: | Execution Team 2022-01-24 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 38 | ||||||||
| Description |
|
The hook for running dbCheck in the background should tolerate SnapshotTooOld error messages. SnapshotTooOld can occur if the primary is slow enough processing a batch that the secondary is unable to obtain the timestamp the primary used. This is particularly significant on server 4.4, where the secondary timestamp retention period is just 5 seconds. |
| Comments |
| Comment by Githook User [ 24/Jan/22 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: (cherry picked from commit ee111876a65ca5f5fdb70c3a0e26eeb57ca79cdd) |
| Comment by Githook User [ 21/Jan/22 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: (cherry picked from commit ee111876a65ca5f5fdb70c3a0e26eeb57ca79cdd) |
| Comment by Githook User [ 20/Jan/22 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: |