nova-scheduler doesn't follow worker-multiplier config in rocky or later
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Cloud Controller Charm |
Fix Released
|
High
|
Nobuto Murata |
Bug Description
In a deployment cloud, nova-c-c unit has more than necessary processes of nova-scheduler (80) while other processes are limited to 20 by worker-
It spawns 240 mysql connection from one unit, so it will be 720 connections from 3 HA units even when the cloud is idle, and potentially kills the cloud when it's loaded.
$ sudo ss -tp | grep :mysql | grep nova-scheduler -c
241
$ pgrep -af nova | cut -d ' ' -f2- | sort | uniq -c
1 bash /etc/systemd/
1 bash /etc/systemd/
21 /usr/bin/python3 /usr/bin/
1 /usr/bin/python3 /usr/bin/
81 /usr/bin/python3 /usr/bin/
1 /usr/bin/python3 /usr/bin/
1 /var/lib/
1 /var/lib/
20 (wsgi:nova-api-os -k start
20 (wsgi:nova_meta) -k start
20 (wsgi:nova-placem -k start
Changed in charm-nova-cloud-controller: | |
assignee: | nobody → Nobuto Murata (nobuto) |
summary: |
- nova-scheduler doesn't follow worker-multiplier config + nova-scheduler doesn't follow worker-multiplier config in rocky or later |
Changed in charm-nova-cloud-controller: | |
importance: | Undecided → High |
Changed in charm-nova-cloud-controller: | |
milestone: | none → 20.10 |
Changed in charm-nova-cloud-controller: | |
status: | Fix Committed → Fix Released |
I think the equivalent config is:
[etc/nova/ nova.conf. sample]
====
[scheduler]
...
#
# Number of workers for the nova-scheduler service. The default will be the
# number of CPUs available if using the "filter_scheduler" scheduler driver,
# otherwise the default will be 1.
# (integer value)
# Minimum value: 0
#workers = <None>
====