multi-node: nova services hit max connections limit
Bug #2023161 reported by
James Page
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Snap |
Triaged
|
Low
|
Unassigned | ||
Bug Description
The current mysql-k8s charm does not configure a maximum connection value based on memory allocation so the default of 151 gets used.
In a multi-node deployment with multiple units of the control plane services, most services are fine and well below 100 concurrent connections to the DB.
Nova however has three databases all in the same mysql instance and as such its connection usage is higher to the same instance - and it does occasionally pass this threshold when it gets busy.
The DPE team are working on dynamic tuning of max connections but we need to put in a workaround for now to increase this threshold.
The number of units won't ever exceed three for the size of deployment we're targeting so 200 should be sufficient.
Revision history for this message
| James Page (james-page) wrote | #1 |
| Changed in snap-openstack: | |
| importance: | Undecided → Critical |
| status: | New → Triaged |
Revision history for this message
| James Page (james-page) wrote | #2 |
| Changed in snap-openstack: | |
| importance: | Critical → Low |
To post a comment you must log in.
https:/