secscan: split indexing of recent manifest into separate background operation (PROJQUAY-3501) #1281
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kleesc
force-pushed
the
secscan-remove-batch-size-pagination
branch
from
f7a1dd2
to
68acf9b
Compare
syed
reviewed
Apr 25, 2022
…peration (PROJQUAY-3501) Index recent manifests in a separate background process, allowing the main process to correctly select random slabs from the entire table set and marking them completed in the allocator (rbtree). This avoids the worker having to start iterating from the beginning of the table whenever it is restarted.
kleesc
force-pushed
the
secscan-remove-batch-size-pagination
branch
from
68acf9b
to
9474d8d
Compare
syed
approved these changes
Apr 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Index recent manifests in a separate background process, allowing the
main process to correctly select random slabs from the entire table
set and marking them completed in the allocator (rbtree). This avoids
the worker having to start iterating from the beginning of the table
whenever it is restarted.