CON-482 Prioritize force wipe syncs #4185
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Tests
Manually tested with local e2e:
A seed create-user
POST <primary>/manually_update_replica_set
and changed 1 secondaryforceWipe = true
andlifo: true
(see below)5. Confirmed other sync jobs with forceWipe not set do not use lifo: true 6. Confirmed new secondary received `sync-processing-queue` jobs with `lifo: false` and correctly synced 7. Confirmed old secondary received `sync-processing-queue` job to forceWipe with lifo:true and correctly executed (see below)
Monitoring - How will this change be monitored? Are there sufficient logs / alerts?
Monitor
recurring-sync-queue
andsync-processing-queue
jobs withforceWipe = true
andlifo = true