Low number of forks results in slow Neutron L3 agent restarts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
In Progress
|
Undecided
|
Adam Oswick |
Bug Description
What happened
-------------
When running a Kolla Ansible deployment with a number of compute nodes greater than the number of forks, the time taken to complete was much greater than n*neutron_
What you expected to happen
-------
The time taken to perform Neutron L3 agent container restarts is approximately equal to n*neutron_
How to reproduce it
-------------------
- Provision an environment with Kolla Ansible that has more than 1 compute node
- Set neutron_
- Modify the Neutron L3 agent neutron.conf files to ensure the containers are restarted on the next run
- Run another Kolla Ansible deployment with the number of forks set to 1
The container restarts will take approximately n*n*neutron_
Environment
-----------
Kolla-Ansible version -> Antelope
Changed in kolla-ansible: | |
assignee: | nobody → Adam Oswick (adamoswick) |
This appears to be due to https:/ /opendev. org/openstack/ kolla-ansible/ commit/ 391aa4677f394f1 581df17fe74da96 8f19981e9d . As this loops through every host, there are hosts*hosts number of tasks to be run with a delay of neutron_ l3_agent_ failover_ delay between each.
That has the expected result when number of forks == number of hosts but if forks is less than hosts then this takes much longer than expected. However, if number of forks is less than this, the process takes much longer even though no changes are actually happening (as the tasks being skipped occupy available forks).