oslo.cache doesn't close connections to memcached
Bug #2043121 reported by
Thomas Goirand
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.cache |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
oslo.cache creates a connection pool to memcached, though the __del__ hasn't been implemented. As a consequence, not-closed connections are left in a CLOSE_WAIT state, which expires after some time (which time depends on the server configuration, as this is customizable with sysctl).
Under a heavy load, such as for example our gnocchi API in production, where we have a huge load every 5 minutes, there's so many CLOSE_WAIT opened sockets that we don't even have any source port available: all 65k ports are left in a CLOSE_WAIT state.
The solution is simple (as per the opened PR): close sockets when the connectionPool is deleted.
Changed in oslo.cache: | |
status: | New → In Progress |
To post a comment you must log in.
A fix proposed to master https:/ /review. opendev. org/c/openstack /oslo.cache/ +/900158