Skip to content

Conversation

FGasper
Copy link
Collaborator

@FGasper FGasper commented Apr 16, 2025

Previously we stored the entire recheck queue in a single collection. This meant that, when we finished a generation, we had to “surgically” delete all rechecks for the old generation.

This changeset alters the metadata so that, rather than a storing rechecks in a single collection, we store them in generation-specific collections like recheckQueue_gen0, recheckQueue_gen1, etc. That way, when we want to clean out a prior generation’s recheck queue, we just drop a collection, which is much faster than deleting 100s of millions of individual recheck documents.

@FGasper FGasper requested review from tdq45gj and autarch April 16, 2025 19:21
Copy link
Collaborator

@tdq45gj tdq45gj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Copy link
Collaborator

@autarch autarch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@FGasper FGasper merged commit ccff9aa into mongodb-labs:main Apr 17, 2025
50 checks passed
@FGasper FGasper deleted the REP-5963-per-generation-recheck branch April 17, 2025 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants