ZeroMQ driver does not close sockets with eventlet 0.9.17
Bug #1099185 reported by
Erica Windisch
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oslo-incubator |
Fix Released
|
Medium
|
Erica Windisch | ||
| Grizzly |
Fix Released
|
Medium
|
Erica Windisch | ||
Bug Description
Due to a change in eventlet.green.zmq per upstream commit 90c9b3b6ade2, the ZeroMQ socket.close() no longer accepts the linger keyword argument. This caused calls to close(linger=-1) to fail, resulting in leaking file descriptors. Eventually systems would error:
"Too many open files (signaler.cpp:330)"
Technically, this is a bug in eventlet.green.zmq failing to accept pyzmq's linger kwarg. However, the default value of linger is already -1, so we can entirely omit the argument.
Additionally, we should at least log an error if a socket cannot be closed.
Does not affect installations with eventlet<0.9.17
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to oslo-incubator (master) | #1 |
| Changed in oslo: | |
| assignee: | nobody → Eric Windisch (ewindisch) |
| status: | New → In Progress |
| summary: |
- ZeroMQ driver does not close sockets with eventlet >0.9.14 + ZeroMQ driver does not close sockets with eventlet 0.9.17 |
| description: | updated |
Revision history for this message
| Erica Windisch (ewindisch) wrote | #2 |
| Changed in oslo: | |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to oslo-incubator (master) | #3 |
| Changed in oslo: | |
| status: | In Progress → Fix Committed |
| Changed in oslo: | |
| milestone: | none → grizzly-3 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/