yahoo-eng-team team mailing list archive

[Max <2033281@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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)

** 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/2033281

Title:
  [OVN] ovn_hash_ring table cleanup

Status in neutron:
  New

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