Bug 1243600 - 1024 mysql connections is not enough on larger hardware
Summary: 1024 mysql connections is not enough on larger hardware
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: Director
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: ga
: 8.0 (Liberty)
Assignee: chris alfonso
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
: 1253526 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-15 21:34 UTC by Ben Nemec
Modified: 2016-04-18 07:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-06 16:08:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ben Nemec 2015-07-15 21:34:59 UTC
Description of problem: On 24 core/48 thread servers, with a 3 node HA deployment, scaling to 20+ compute nodes resulted in a failed tenant instance boot because the mysql connection limit was reached.  Even idle, the connection count was sitting around 900.


Version-Release number of selected component (if applicable):


How reproducible: On any hardware with a lot of cores.


Steps to Reproduce:
1. Deploy with OSP director on hardware with 48 or more threads available.
2. Attempt to do anything significant on the overcloud.
3.

Actual results: 500 errors from services due to no available mysql connections.


Expected results: Working overcloud


Additional info: This is likely because we scale the api processes based on number of cores, and 48 api processes across three controllers adds up to a lot of mysql connections.  We need to increase the default, or make it configurable.

Comment 4 Mike Burns 2015-08-14 05:25:05 UTC
*** Bug 1253526 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.