Bug 1253526 - Increase the MySQL max_connections on the undercloud
Summary: Increase the MySQL max_connections on the undercloud
Keywords:
Status: CLOSED DUPLICATE of bug 1243600
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: Director
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: Director
Assignee: chris alfonso
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-14 02:22 UTC by Gaëtan Trellu
Modified: 2016-04-18 06:51 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-14 05:25:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gaëtan Trellu 2015-08-14 02:22:16 UTC
Description of problem:

During an Heat stack deletion, the stack failed and we are unable to remove it even after many retries.
We can see MySQL max_connection errors in the Heat logs:

   OperationalError: (_mysql_exceptions.OperationalError) (1040, 'Too many connections')\n"]."

The full log is in the "Additional info" section.

After raised the max_connections to 2048, I was able to delete the Heat stack.

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

rhos-release-0.66-1.noarch
python-rdomanager-oscplugin-0.0.8-44.el7ost.noarch
puddle images 2015-07-30.1

How reproducible:

It can be reproduce with big Heat stack, like 10 nodes to deploy.

Steps to Reproduce:
1. Heat stack deployment
2. Heat stack deletion

Actual results:

Unable to delete the Heat stack even after many retries.

Expected results:

Be able to delete an Heat stack without error.

Additional info:

Heat error logs: http://pastebin.test.redhat.com/305355

Comment 3 Mike Burns 2015-08-14 05:25:05 UTC

*** This bug has been marked as a duplicate of bug 1243600 ***


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