| 2013-01-13 20:46:18 |
Erica Windisch |
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. |
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 |
|
