Configure SQLAlchemy connection pool for production sized environments
Bug #1274784 reported by
Dmitry Borodaenko
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Aleksandr Didenko | ||
5.0.x |
Fix Committed
|
High
|
Aleksandr Didenko | ||
5.1.x |
Fix Committed
|
High
|
Aleksandr Didenko | ||
6.0.x |
Fix Committed
|
High
|
Aleksandr Didenko | ||
6.1.x |
Fix Committed
|
High
|
Aleksandr Didenko |
Bug Description
Fuel should configure Nova, Neutron, Cinder, and Glance with SQLAlchemy connection pool size parameters (min_pool_size, max_pool_size, overflow etc.) increased from the OpenStack defaults to values suitable to fully utilize a typical server system with 48 hardware threads available (2 CPUS x 12 cores x 2 HT), e.g. 32 connections per service.
MySQL server connection limit (max_connections) should be increased to accomodate all services, e.g. 512 connections per server.
A configuration with all connections utilized simultaneously should be verified to confirm whether file descriptor limit for MySQL should be increased from the default of 1024 as well.
Changed in fuel: | |
status: | New → Triaged |
tags: | added: customer-found |
Changed in fuel: | |
assignee: | Matthew Mosesohn (raytrac3r) → Fuel Library Team (fuel-library) |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Bogdan Dobrelya (bogdando) |
Changed in fuel: | |
milestone: | 4.1 → 5.0 |
Changed in fuel: | |
milestone: | 4.1.1 → 5.0 |
tags: | added: release-notes |
tags: | added: release-notes-done |
To post a comment you must log in.
This is related to my work on https:/ /bugs.launchpad .net/fuel/ +bug/1270875. I am trying to implement this in a way that scales with the # of CPU cores available to the system and amount of total memory available.
It makes little sense to set up 48 threads on a 1 core VM with 1.5gb memory, so I've been working on using facter facts to get these values correctly sized.