feat: add concurrency limit for WAL replay #26483
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.
WAL replay currently loads all WAL files concurrently running into OOM. This commit adds a CLI parameter
--wal-replay-concurrency-limit
that would allow the user to set a lower limit and run WAL replay again.Also, small refactor to introduce args struct to hold the all the params to
WalObjectStore::new
method and remove#[allow(clippy::too_many_arguments)]
.CLI changes added to WAL section as below,
closes: #26481
Tests
Another set of tests to prove that without setting concurrency limit it definitely loads all the WAL files and the time it takes is roughly equivalent. In this setup, there were 39 files (~3.8M) and they all loaded in ~6s.