FYI
from the source for eventlet/green/ssl.py:
Python nonblocking ssl objects don't give errors when the other
end of the socket is closed (they do notice when the other end is
shutdown, though). Any write/read operations will simply hang if
the socket is closed from the other end. There is no obvious fix
for this problem; it appears to be a limitation of Python's ssl
object implementation. A workaround is to set a reasonable timeout
on the socket using settimeout(), and to close/reopen the
connection when a timeout occurs at an unexpected juncture in the
code.
In my opinion, SSL should never be run in the python for any production
system and would advocate removing SSL from swift all together to prevent
future headaches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959221
Title:
swift consumes over 100% of cpu during upload
To manage notifications about this bug go to:
https://bugs.launchpad.net/swift/+bug/959221/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
