[openstack-dev] [neutron] does neutron actually use the salve_connection ?

cristi.calin at orange.com cristi.calin at orange.com
Thu Jun 15 12:47:42 UTC 2017


I am looking to improve the database load distribution and one of the things that may help with this is to spread out the reads.
>From the configuration reference it looks like neutron dues support a slave_connection parameter but when I enabled it and enabled query logging on the secondary databases there aren't any queries being executed on the secondaries. Is there anything I am missing ?

Sorry for CC'ing the dev list as well but someone in the dev teams may have an answer from a developer point of view.

My setup is like this:

Openstack stable/mitaka (built from git)
3 galera nodes
1 haproxy running on each node with active/backup with local node as single active configuration for the frontend listening on :3306 and active/backup with the other nodes as active for the frontend listening on :3308

In neutron.conf in the [database] section I set up the the connection and slave_connection parameters like this:

connection = mysql+pymysql://neutron:XXXXXXX@neutron-db.service:3306/neutron?charset=utf8
slave_connection = mysql+pymysql://neutron: XXXXXXX at neutron-db.service:3308/neutron?charset=utf8
idle_timeout = 1800
max_retries = -1
retry_interval = 5
min_pool_size = 8
max_pool_size = 32
max_overflow = 16

Loooking on a slave it opens a single connection which is eventually closed because of lack of activity.



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170615/2fc367d7/attachment.html>

More information about the OpenStack-dev mailing list