Bump catchup RAM burst limit to match other pubnet mission limit#408
Merged
Conversation
PR stellar#404 bumped RAM burst limits to account for the RAM usage increase in in-memory rebuild on pubnet. However, parallel catchup uses a different resource specification and so runs in into the same OOM issue that stellar#404 resolved. This PR bumps the catchup burst RAM limit to match the limit in stellar#404.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR increases the Kubernetes memory burst limit for the parallel catchup mission to align with the higher pubnet RAM limits introduced in PR #404, preventing OOM kills during in-memory rebuild peaks.
Changes:
- Bump
ParallelCatchupCoreResourceRequirementsmemory limit from16384Mito24000Mi. - Update the inline comment describing the parallel catchup resource spec (though the units in the comment should be corrected; see review comment).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
anupsdf
approved these changes
Jul 14, 2026
This file contains hidden or 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
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.
PR #404 bumped RAM burst limits to account for the RAM usage increase in in-memory rebuild on pubnet. However, parallel catchup uses a different resource specification and so runs in into the same OOM issue that #404 resolved. This PR bumps the catchup burst RAM limit to match the limit in #404.