rpc.(multi)call has no timeout waiting for responses
Bug #843200 reported by
Chris Behrens
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Medium
|
Russell Bryant | ||
Bug Description
When nova does an rpc.call/multicall, it generates a unique queue for a response and waits forever to receive this response.
If the daemon that consumed the 'call' request is restarted in the middle of processing the request (post-ACKing the amqp message), the processing of the request would be killed and not restarted upon daemon restart. This means that it would never put a message in the response queue for the caller. This leaves the initial caller waiting forever, blocking a greenthread and holding an RPC connection out of the pool.
| Changed in nova: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
| Changed in nova: | |
| assignee: | nobody → Russell Bryant (russellb) |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #2 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → essex-4 |
| Changed in nova: | |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/