charm-neutron-api/templates/parts
Trent Lloyd 074e577791 Remove database max_pool_size customisation
The database pool size is per-worker and not shared among the workers.
Currently we incorrectly scale max_pool_size with the worker count,
resulting in an excessive number of database connections that are both
unnecessary and can exhaust the MySQL server max_connections.

With the previous formula max_pool_size = workers * 4, the resulting
connection count was exponential e.g. with 10 workers you get 400
connections but with 20 workers you get 1600. With the commonly deployed
setting of worker-multiplier=0.25 you get 20 workers on 40C/80T machines
and a 3 node HA setup was consuming 3 * 1600 = 4800 MySQL connections.

This customisation was added when rpc_workers support was added (commit
b6ff05ddfe) and I cannot find any evidence that a higher pool count is
needed, the upstream neutron project also removed it's own customisation
of 10 in deference to the oslo.db default of (LP: #1682307). So this
change appears safe and will result in only 100 connections for 20
workers instead of 1600.

Closes-Bug: #1905810
Change-Id: I39b0c17a9ca04c254b08331ac10198680ce1fa28
2020-12-17 18:50:11 +00:00
..
database Principle for Neutron API 2014-06-05 11:59:00 +01:00
rabbitmq Principle for Neutron API 2014-06-05 11:59:00 +01:00
section-database Remove database max_pool_size customisation 2020-12-17 18:50:11 +00:00
section-designate Fix creds for keystone v3 deploys with designate 2018-03-05 17:13:30 +00:00
section-infoblox Add support for Infoblox IPAM configuration via subordinate charm. 2019-06-20 12:03:28 -04:00
section-nova Add support for Infoblox IPAM configuration via subordinate charm. 2019-06-20 12:03:28 -04:00
section-placement add segments service_plugin to neutron-api 2018-01-20 23:14:26 +03:00