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.
- Votes:
-
0 Vote for this issue
- Watchers:
-
3 Start watching this issue
- Created:
- Updated:
- Resolved: