network_rpcapi.allocate_for_instance timing out under load.

Bug #1158552 reported by Joe Gordon
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Unassigned

Bug Description

Environment:

* devstack with nova Grizzly-RC1
* 'compute_driver = nova.virt.fake.FakeDriver' in nova.conf
* following nova branch https://github.com/jogo/nova/commits/perf_logging (commit c55372908de3e66bc000ebb9dd17f688b4914101)
* no quantum

when trying to run 50 VMs in devstack using 'euca-run-instances ami-00000003 -t m1.micro -n 100'

I see network_rpcapi.allocate_for_instance occasionally RPC timing out (call from nova-compute to nova-network).

nova-compute log http://paste.openstack.org/show/34252/
nova-network log http://paste.openstack.org/show/34255/

Joe Gordon (jogo)
description: updated
Revision history for this message
Vish Ishaya (vishvananda) wrote :

I suspect you are running into iptables lock contention. I'm not sure if there is a good fix for this besides updating the rpc timeout.

Changed in nova:
status: New → Incomplete
Revision history for this message
Joe Gordon (jogo) wrote :

I am surprised we are seeing this break with just 50 VMs.

Revision history for this message
Matt Riedemann (mriedem) wrote :

Maybe this is a duplicate of bug 1311778?

Revision history for this message
Joe Gordon (jogo) wrote :

This has been fixed.

Changed in nova:
status: Incomplete → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → kilo-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: kilo-1 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.