Merged
Conversation
Member
Author
|
@cityofships reported it reaching ~30GB |
Member
Author
|
Debug info: Top 10 objects before patch, approx ~30 scrapes: Top 10 objects before patch, no scrapes: Note, no high count for Top 10 objects with patch, approx 30 scrapes: Top 10 objects, closing the connection after each scrape, approx 30 scrapes: ^ NOTE: this /should/ clean up, but it doesn't |
Every time the collector is scraped, it makes a new connection. The connection is never cleaned up, even if you add a conn.close() after the scrape [1]. This is a likely bug. This patch moves to using the instance connection, which works around the leak and is more efficient. [1] https://docs.openstack.org/openstacksdk/latest/user/connection.html#openstack.connection.Connection.close
9eecc6a to
3cad01a
Compare
m-bull
approved these changes
Oct 17, 2025
Member
Author
thanks for the review! |
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.
Every time the collector is scraped, it makes a new connection. The connection is never cleaned up, even if you add a conn.close() after the scrape [1]. This is a likely bug.
This patch moves to using the instance connection, which works around the leak and is more efficient.
[1] https://docs.openstack.org/openstacksdk/latest/user/connection.html#openstack.connection.Connection.close