liberty: ~busy loop on epoll_wait being called with zero timeout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Medium
|
Unassigned | ||
Kilo |
Fix Released
|
Medium
|
Unassigned | ||
Liberty |
Fix Released
|
Medium
|
Unassigned | ||
Mitaka |
Fix Released
|
Medium
|
Unassigned | ||
Newton |
Fix Released
|
Medium
|
Unassigned | ||
oslo.messaging |
Fix Released
|
Undecided
|
John Eckersberg | ||
python-oslo.messaging (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned | ||
Yakkety |
Fix Released
|
Medium
|
Unassigned | ||
Zesty |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Context: openstack juju/maas deploy using 1510 charms release
on trusty, with:
openstack-origin: "cloud:
source: "cloud:
* Several openstack nova- and neutron- services, at least:
nova-compute, neutron-server, nova-conductor,
neutron-
show almost busy looping on epoll_wait() calls, with zero timeout set
most frequently.
- nova-compute (chose it b/cos single proc'd) strace and ltrace captures:
http://
As comparison, this is how it looks on a kilo deploy:
- http://
* 'top' sample from a nova-cloud-
this completely idle stack:
http://
FYI *not* seeing this behavior on keystone, glance, cinder,
ceilometer-api.
As this issue is present on several components, it likely comes
from common libraries (oslo concurrency?), fyi filed the bug to
nova itself as a starting point for debugging.
Note: The description in the following bug gives a good overview of the issue and points to a possible fix for oslo.messaging: https:/
description: | updated |
description: | updated |
Changed in nova (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in oslo.messaging: | |
assignee: | nobody → John Eckersberg (jeckersb) |
status: | Incomplete → In Progress |
Changed in oslo.messaging: | |
assignee: | John Eckersberg (jeckersb) → Gevorg Davoian (gdavoian) |
Changed in oslo.messaging: | |
assignee: | Gevorg Davoian (gdavoian) → nobody |
Changed in oslo.messaging: | |
assignee: | nobody → John Eckersberg (jeckersb) |
no longer affects: | nova (Ubuntu Trusty) |
no longer affects: | nova (Ubuntu Xenial) |
no longer affects: | nova (Ubuntu Yakkety) |
no longer affects: | nova (Ubuntu Zesty) |
Changed in python-oslo.messaging (Ubuntu Zesty): | |
status: | New → Fix Released |
affects: | nova → ubuntu-translations |
no longer affects: | ubuntu-translations |
no longer affects: | nova (Ubuntu) |
Changed in cloud-archive: | |
importance: | Undecided → Medium |
Changed in python-oslo.messaging (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in python-oslo.messaging (Ubuntu Yakkety): | |
importance: | Undecided → Medium |
Changed in python-oslo.messaging (Ubuntu Zesty): | |
importance: | Undecided → Medium |
tags: |
added: verification-done removed: verification-needed |
tags: |
added: verification-liberty-done removed: verification-liberty-needed |
tags: |
added: verification-mitaka-done removed: verification-mitaka-needed |
Changed in cloud-archive: | |
status: | Fix Committed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.