[Openstack] [OVS] Loopingcall and high load on nova comp
Hi guys, i seen on each nova compute node a ressource overhead caused by quantum ovs agent. This means if only runs the agent on the compute node (+ nova-compute) i'll have sometimes a load by 2. The agent will have a many cpu hours and if i take a look into the log file i see manytimes this one: 2013-05-17 12:35:46 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.195565 sec 2013-05-17 12:35:50 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.24272 sec 2013-05-17 12:35:54 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.254162 sec 2013-05-17 12:35:58 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.131815 sec 2013-05-17 12:36:02 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.213518 sec 2013-05-17 12:36:07 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.212293 sec 2013-05-17 12:36:11 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.223576 sec I've searched to this warning but without success. Anyone have an idea or the same problem ? Greetings Heiko ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OVS] Loopingcall and high load on nova comp
Hi! This means that this loopingcall will be running in a hard loop (no delay between runs) because it is taking longer than the interval it has requested to be called at. Either we need to change the interval (if that's ok, no idea with Quantum), or we need to make the work being done in a loop faster. Hope that helps, Michael On Fri, May 17, 2013 at 8:41 PM, Heiko Krämer i...@honeybutcher.de wrote: Hi guys, i seen on each nova compute node a ressource overhead caused by quantum ovs agent. This means if only runs the agent on the compute node (+ nova-compute) i'll have sometimes a load by 2. The agent will have a many cpu hours and if i take a look into the log file i see manytimes this one: 2013-05-17 12:35:46 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.195565 sec 2013-05-17 12:35:50 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.24272 sec 2013-05-17 12:35:54 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.254162 sec 2013-05-17 12:35:58 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.131815 sec 2013-05-17 12:36:02 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.213518 sec 2013-05-17 12:36:07 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.212293 sec 2013-05-17 12:36:11 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.223576 sec I've searched to this warning but without success. Anyone have an idea or the same problem ? Greetings Heiko ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OVS] Loopingcall and high load on nova comp
Unsubscribe On Friday, May 17, 2013, Heiko Krämer wrote: Hi guys, i seen on each nova compute node a ressource overhead caused by quantum ovs agent. This means if only runs the agent on the compute node (+ nova-compute) i'll have sometimes a load by 2. The agent will have a many cpu hours and if i take a look into the log file i see manytimes this one: 2013-05-17 12:35:46 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.195565 sec 2013-05-17 12:35:50 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.24272 sec 2013-05-17 12:35:54 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.254162 sec 2013-05-17 12:35:58 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.131815 sec 2013-05-17 12:36:02 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.213518 sec 2013-05-17 12:36:07 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.212293 sec 2013-05-17 12:36:11 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.223576 sec I've searched to this warning but without success. Anyone have an idea or the same problem ? Greetings Heiko ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net javascript:; Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp