RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1297692 - Raise MariaDB max connections limit
Summary: Raise MariaDB max connections limit
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: trunk
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: trunk
Assignee: Ivan Chavero
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-12 09:07 UTC by Marko Myllynen
Modified: 2023-09-14 03:16 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-08-18 19:20:47 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 269181 0 None ABANDONED Change mariadb max connection limit 2020-08-18 19:20:27 UTC

Description Marko Myllynen 2016-01-12 09:07:05 UTC
Description of problem:
PackStack sets MariaDB max connections limit to 1024 which is rather easily hit in NFV/VNF PoC environments. Please consider raising the default limit, for example to something like 4096. Thanks.

Comment 5 Christopher Brown 2017-06-18 06:48:43 UTC
Upstream patch was abandoned, I think this is generally left as a "tunable parameter" for user to set as appropriate.

Much debate over sensible defaults, e.g.

https://bugzilla.redhat.com/show_bug.cgi?id=1240824

Perhaps update if this is still a requirement?

Comment 6 Marko Myllynen 2017-06-19 06:40:27 UTC
(In reply to Christopher Brown from comment #5)
> 
> Perhaps update if this is still a requirement?

Nothing has changed since the initial comment, this is still needed in some environments but if upstream is not willing to change the default we can live with this. Thanks.

Comment 7 Christopher Brown 2017-06-19 08:05:50 UTC
Would be good to get a comment from upstream then. Setting needinfo...

Comment 8 Red Hat Bugzilla 2023-09-14 03:16:00 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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