Public bug reported: The revision_number is used to check if the message received at the agent is stale or not. However neutron doesn't consider a message as stale if the revision_number in NetworkCache is equal to the revision_number of the incoming payload. It is only considered stale if the revision_number in NetworkCache is greater than the revision_number in incoming payload
https://opendev.org/openstack/neutron/src/commit/10230683a2ce2f26279feaa34af4c0eccbfcb16c/neutron/agent/dhcp/agent.py#L852 Because of this lot more messages not considered as stale even though they are. This causes lot of "reload_allocations" and dhcp reloads and can cause bottlenecks in busy openstack environments. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1874400 Title: [agent][dhcp] When revision_number matches the one in cache it is not considered stale Status in neutron: New Bug description: The revision_number is used to check if the message received at the agent is stale or not. However neutron doesn't consider a message as stale if the revision_number in NetworkCache is equal to the revision_number of the incoming payload. It is only considered stale if the revision_number in NetworkCache is greater than the revision_number in incoming payload https://opendev.org/openstack/neutron/src/commit/10230683a2ce2f26279feaa34af4c0eccbfcb16c/neutron/agent/dhcp/agent.py#L852 Because of this lot more messages not considered as stale even though they are. This causes lot of "reload_allocations" and dhcp reloads and can cause bottlenecks in busy openstack environments. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1874400/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp