Increase memory limit for MSOutput and MSRuleCleaner to 1Gi #1527
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
arooshap
approved these changes
Jul 18, 2024
|
@amaltaro sure, please proceed! :) |
|
Thanks Aroosha. Right now we cannot push in these limits because both MSOutput and MSRuleCleaner are under stress, and they were getting killed even with 1.25GB. I edit'ed the deployment template of those 2 services to limit it to 2GB. I think we can roll it back to the 1GB provided in this PR, in the beginning of the next week. So we can either merge it now, or wait until the next week or so. Thanks |
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.
Fixes dmwm/WMCore#12042
It is a small memory limit increase, but it should help us to better deal with peak loads in these microservices, especially after outages and/or misbehaviors of the services.