Profile shows that eventlet/green/ssl.py is the culprit. Look at call
numbers and cumulative time.
** Attachment added: "profile 1"
https://bugs.launchpad.net/swift/+bug/959221/+attachment/3035280/+files/lp959221.prof1.txt
--
You received this bug notification because you are a member of Ubu
It looks like the problem may be looping. If I do the following slew of
hand, CPU burn dissipates:
--- /usr/lib/python2.7/site-packages/eventlet/green/ssl.py.fcs 2012-04-09
19:32:04.516730732 -0600
+++ /usr/lib/python2.7/site-packages/eventlet/green/ssl.py 2012-04-09
21:49:38.823537699 -06
Roman, please try this and let us know if it works for you.
** Patch added: "patch 2, test workaround"
https://bugs.launchpad.net/swift/+bug/959221/+attachment/3041102/+files/swift-lp959221-2.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
This works, too:
[root@lembas green]# pwd
/usr/lib/python2.7/site-packages/eventlet/green
[root@lembas green]# diff -u ssl.py.fcs ssl.py
--- ssl.py.fcs 2012-04-10 08:54:43.257885841 -0600
+++ ssl.py 2012-04-10 08:56:27.282585355 -0600
@@ -129,7 +129,10 @@
count = 0
This reproduces easily on my laptop, running Fedora 16, using git tip
swift client (1.4.10). The problem definitely has something with SSL. I
created a 2-node Swift+Keystone to be accessible through Pound, and
configured Pound to allow both plain HTTP and SSL. Uploads with HTTP
only use up a worryi
Fix releases in Havana release of OpenStack.
** Changed in: python-swiftclient
Status: Fix Committed => Fix Released
--
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 consume
Just to clarify: my patch does not remove SSL at all. SSL is there and
works as before. The only difference is that it's not trampolined into
eventlet anymore. The root cause is the conflict between eventlet's
green threads, which require faking of blocking sockets, and SSL, which
requires looping
** Changed in: swift
Status: New => Confirmed
--
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
** Changed in: swift
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920197
Title:
[SRU] webob last stable version 1.1.1 response header bug
To manage notifications ab
see also https://review.openstack.org/22569
--
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:
h
** Changed in: swift
Assignee: Flavio Percoco (flaper87) => Pete Zaitcev (zaitcev)
--
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
Fixed in:
https://github.com/openstack/python-swiftclient/commit/3196daf9929eef25d69d47592beef4cd31573b80
For some reason, Jenkins and Gerrit did not close the bug.
** Changed in: swift
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of
** Patch added: "Fix as committed"
https://bugs.launchpad.net/ubuntu/+source/swift/+bug/959221/+attachment/3675321/+files/python-swiftclient-1.4-lp959221-2.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I like David's fix with two subprocess.Popen and a loop that forks the stream.
I would've preferred the same approach myself, but I did not have Python
chops to do it.
BTW, I have RT # now, for next time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
14 matches
Mail list logo
