>From: ext Chris Friesen [mailto:chris.frie...@windriver.com] >Sent: Monday, May 11, 2015 6:09 PM >To: openstack-dev@lists.openstack.org >Subject: Re: [openstack-dev] [nova] Service group foundations and features > >On 05/11/2015 07:13 AM, Attila Fazekas wrote: >>> From: "John Garbutt" <j...@johngarbutt.com> > >>> * From the RPC api point of view, do we want to send a cast to >>> something that we know is dead, maybe we want to? Should we wait for >>> calls to timeout, or give up quicker? >> >> How to fail sooner: >> https://bugs.launchpad.net/oslo.messaging/+bug/1437955 >> >> We do not need a dedicated is_up just for this. > >Is that really going to help? As I understand it if nova-compute dies (or is >isolated) then the queue remains present on the server but nothing will >process >messages from it. > >Chris
for queued messages if the forced_down proposed in https://review.openstack.org/#/c/169836/ is set to true, "I'm up" message should be ignored until this forced_down is cleared as this flag is there also to prevent service state to turn 'up'. So flag is there to have fast way to state service is down to enable evacuate (prevent scheduling VM to host..), but also to prevent invalid state. Even abort nova-compute startup as mentioned in review comments. This should make things quite safe. -Tomi __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
