Why don't we put the agent heartbeat into a separate greenthread on the agent so it continues to send updates even when it's busy processing changes? On Jun 4, 2015 2:56 AM, "Anna Kamyshnikova" <akamyshnik...@mirantis.com> wrote:
> Hi, neutrons! > > Some time ago I discovered a bug for l3 agent rescheduling [1]. When there > are a lot of resources and agent_down_time is not big enough neutron-server > starts marking l3 agents as dead. The same issue has been discovered and > fixed for DHCP-agents. I proposed a change similar to those that were done > for DHCP-agents. [2] > > There is no unified opinion on this bug and proposed change, so I want to > ask developers whether it worth to continue work on this patch or not. > > [1] - https://bugs.launchpad.net/neutron/+bug/1440761 > [2] - https://review.openstack.org/171592 > > -- > Regards, > Ann Kamyshnikova > Mirantis, Inc > > __________________________________________________________________________ > 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
