Conversation
egegunes
previously approved these changes
Oct 29, 2025
egegunes
approved these changes
Oct 29, 2025
gkech
approved these changes
Oct 29, 2025
Collaborator
commit: 8ff553e |
egegunes
pushed a commit
that referenced
this pull request
Oct 29, 2025
* fix con * fix lint and add test * log pbm connection closing error & improve error message in e2e test * uniform error messages for e2e test --------- Co-authored-by: George Kechagias <george.kechagias@percona.com>
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.
CHANGE DESCRIPTION
Problem:
In various places inside the code, when we are calling
pbm, err := backup.NewPBM(ctx, r.client, cr), we never actually callpbm.Close(ctx). This leads to connections piling up leading eventually to OOMKilled.Related issue: https://forums.percona.com/t/percona-operator-for-mongodb-endlessly-spawning-connections-until-oomkilled/39634
Cause:
Short explanation of the root cause of the issue if applicable.
Solution:
Properly closing the connections keeps everything normal
Adjusted also the e2e test init-deploy to verify that connections don't grow over a specific sanity limit.
CHECKLIST
Jira
Needs Doc) and QA (Needs QA)?Tests
compare/*-oc.yml)?Config/Logging/Testability