Re: [openstack-dev] [nova] expected behaviour of _report_state() on rabbitmq failover

2014-09-21 Thread Matt Riedemann
On 9/10/2014 3:33 PM, Chris Friesen wrote: On 09/10/2014 02:13 PM, Chris Friesen wrote: As it stands, it seems that waiting for the RPC call to time out blocks _report_state() from running again in report_interval seconds, which delays the service update until the RPC timeout period expires.

Re: [openstack-dev] [nova] expected behaviour of _report_state() on rabbitmq failover

2014-09-21 Thread Matt Riedemann
On 9/21/2014 7:56 PM, Matt Riedemann wrote: On 9/10/2014 3:33 PM, Chris Friesen wrote: On 09/10/2014 02:13 PM, Chris Friesen wrote: As it stands, it seems that waiting for the RPC call to time out blocks _report_state() from running again in report_interval seconds, which delays the

[openstack-dev] [nova] expected behaviour of _report_state() on rabbitmq failover

2014-09-10 Thread Chris Friesen
Hi, I'm running Havana and I'm seeing some less-than-ideal behaviour on rabbitmq failover. I'd like to figure out if this is expected behaviour or if something is going wrong. We're running rabbitmq in active/standby mode with DRBD storage. On the controller the timeline looks like this:

Re: [openstack-dev] [nova] expected behaviour of _report_state() on rabbitmq failover

2014-09-10 Thread Chris Friesen
On 09/10/2014 02:13 PM, Chris Friesen wrote: As it stands, it seems that waiting for the RPC call to time out blocks _report_state() from running again in report_interval seconds, which delays the service update until the RPC timeout period expires. Just noticed something... In the case of