This repository was archived by the owner on Nov 6, 2020. It is now read-only.
Fix OOM when restoring a Snapshot #9088
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.
Fixes #8825
The issue was that snapshot chunks were fetched at random, meaning that if an account would be divided into multiple chunks (because it was too big to fit in one), the extracted data would sit in memory until the last chunk of the account is fetched and processed; thus causing increasing memory usage until everything can be flushed in DB, and this would trigger an OOM.
This fix is thus quite simple : fetch the chunks in the right order.