Thanks for responding, does this make it longest by time duration thread ever? :)
2015-10-15 22:44 GMT+02:00 Thomas Goirand <z...@debian.org>: > On 12/16/2014 11:59 AM, Alan Pevec wrote: ... >> Current implementation in oslo service sends notification only just >> before entering the wait loop, because at that point all >> initialization should be done and service ready to serve. Does anyone >> have a suggestion for the better place where to notify service >> readiness? > What you describe above looks like a defect in the implementation. Of > course, waiting for more than 90s should be considered as failed, and I > wouldn't want in any case to have this timeout increased. Failed > attempts to connect to Rabbit shouldn't, IMO, be the cause for not > sending the notify signal. But if service requires message bus for normal operations, it is not ready to server requests, is it? Cheers, Alan __________________________________________________________________________ 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