Bump parallel catchup RAM requests #348
Merged
Conversation
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
This PR bumps prallel catchup worker pod RAM requests from 2 to 8G. I noticed that the pods burst quite a lot and having requests so low when compared to 16G limit means k8s may need to kill pods sometimes due to memory contention.
jayz22
approved these changes
Dec 4, 2025
Contributor
jayz22
left a comment
jayz22
left a comment
There was a problem hiding this comment.
It's okay to bump this, especially if we are using more than it anyway. We need to monitor it case the cluster don't have enough memory to guarantee for all pods.
Contributor
|
Approved, we can merge this after cutting core v25-rc2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR bumps parallel catchup worker pod RAM requests from 2 to 8G.
I noticed that the pods burst quite a lot and having requests so low when compared to 16G limit means k8s may need to kill pods sometimes due to memory contention.