-
Notifications
You must be signed in to change notification settings - Fork 807
Ensure collection of stats succeed in a maximum duration to avoid exhausting PG connections #1229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
pierresouchay
wants to merge
7
commits into
prometheus-community:master
Choose a base branch
from
pierresouchay:limit_max_duration_of_postgresql_connections_to_avoid_using_too_many_connections
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+101
−4
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
443e086 to
26a21a6
Compare
**Context**: As explained in prometheus-community#1228, when database is very slow to answer, every call to prometheus exporter might consume a new connection and possibly consume all available connections **Solution**: Ensure a Context with a specified Timeout is specified, so the connection will end if duration of collection is too long Signed-off-by: Pierre Souchay <pierre.souchay@pelico.io>
ba8c19c to
76203d5
Compare
…should Signed-off-by: Pierre Souchay <pierre.souchay@pelico.io>
76203d5 to
f588ca8
Compare
…DME.md Signed-off-by: Pierre SOUCHAY <pierre.souchay@pelico.io>
sysadmind
reviewed
Dec 12, 2025
Signed-off-by: Pierre SOUCHAY <pierre.souchay@pelico.io>
Signed-off-by: Pierre SOUCHAY <pierre.souchay@pelico.io>
Signed-off-by: Pierre SOUCHAY <pierre.souchay@pelico.io>
…ns_to_avoid_using_too_many_connections
Author
|
@sysadmind I think I addressed all of your concerns, thank you very much for the review |
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.
Context: As explained in #1228, when database is very slow to answer, every call to prometheus exporter might consume a new connection and possibly consume all available connections
Solution: Ensure a Context with a specified Timeout is specified, so the connection will end if duration of collection is too long
Will fix #1228