Reviewed: https://review.opendev.org/c/openstack/neutron/+/893030 Committed: https://opendev.org/openstack/neutron/commit/7f777c223e557f7bb0e0290090019eaa60095b50 Submitter: "Zuul (22348)" Branch: master
commit 7f777c223e557f7bb0e0290090019eaa60095b50 Author: Lucas Alvares Gomes <[email protected]> Date: Tue Aug 29 11:37:52 2023 +0100 [OVN] Cleanup old Hash Ring node entries This patch introduces a maintenance task that runs once a day and is responsible for cleaning up Hash Ring nodes that haven't been updated in 5 days or more. Change-Id: Ibed9e0d77500570c3d0f9f39bfe40cb9239d0d7a Closes-Bug: #2033281 Signed-off-by: Lucas Alvares Gomes <[email protected]> ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2033281 Title: [OVN] ovn_hash_ring table cleanup Status in neutron: Fix Released Bug description: The ovn hash ring implementation is currently based on the hostname. Does it make sense to implement a periodic cleanup job? E.g. clean offline nodes which are older than 7 days or so. In our environment, the ovn_hash_ring table grows a lot because our API runs containerized with random hostnames (e.g. neutron- api-5fc8ffb45-dl86p). This means with every api restart we have 64 new entries due to 64 api_workers. MariaDB [neutron]> select count(*) from ovn_hash_ring; +----------+ | count(*) | +----------+ | 80957 | +----------+ 1 row in set (0.003 sec) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2033281/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
