Bug 1387692 - [OSP7] Set default haproxy client/server timeout for mysql to 90m
Summary: [OSP7] Set default haproxy client/server timeout for mysql to 90m
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: zstream
: 7.0 (Kilo)
Assignee: Jiri Stransky
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-21 15:01 UTC by Ondrej
Modified: 2022-08-09 15:22 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-20 08:35:04 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-7889 0 None None None 2022-08-09 15:22:02 UTC
Red Hat Knowledge Base (Solution) 1595673 0 None None None 2016-10-21 15:02:13 UTC

Description Ondrej 2016-10-21 15:01:34 UTC 
Description of problem:
Hi,
can haproxy mysql client/server timeout be set to 90m in director templates by default? As currently is set to 0, that keeps a lot of connections stuck and has to be changed every time manually anyway.

Higher versions of OSP are by default deployed with 1m timeout values.


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


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


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