rpc layer should use a threadpool or some other magic to add concurrency
Bug #718994 reported by
Soren Hansen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
If you ask a compute worker to fire up an instance, that could take a while. Some of the operations involved can be quite time consuming, especially if you're not using cow images. All the while, the worker is unable to respond to rpc calls. This means that someone trying to get the console output of a running instance on the same box might have to wait *minutes* for a response. That's not cool.
Related branches
lp:~soren/nova/rpc-threadpool
- Devin Carlen (community): Approve
- Jay Pipes (community): Approve
-
Diff: 37 lines (+8/-1)1 file modifiednova/rpc.py (+8/-1)
Changed in nova: | |
status: | New → Fix Committed |
Changed in nova: | |
milestone: | none → 2011.2 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.