Bug 1726733 - Default amphora timeouts too high for production environments
Summary: Default amphora timeouts too high for production environments
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z11
: 13.0 (Queens)
Assignee: Carlos Goncalves
QA Contact: Bruna Bonguardo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-03 15:14 UTC by Carlos Goncalves
Modified: 2020-03-10 11:18 UTC (History)
6 users (show)

Fixed In Version: openstack-tripleo-heat-templates-8.4.1-22.el7ost
Doc Type: Enhancement
Doc Text:
This enhancement provides default Octavia timeouts that are suitable for production environments, and the following new heat parameters to override the defaults: * OctaviaConnectionMaxRetries * OctaviaBuildActiveRetries * OctaviaPortDetachTimeout
Clone Of:
Environment:
Last Closed: 2020-03-10 11:18:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 682636 0 'None' MERGED Add build_active_retries and port_detach_timeout 2020-11-24 14:38:09 UTC
OpenStack gerrit 682641 0 'None' MERGED Add new parameter options to Octavia service 2020-11-24 14:38:33 UTC
OpenStack gerrit 683782 0 'None' MERGED Add build_active_retries and port_detach_timeout 2020-11-24 14:38:33 UTC
OpenStack gerrit 685363 0 'None' MERGED Add new parameter options to Octavia service 2020-11-24 14:38:10 UTC

Description Carlos Goncalves 2019-07-03 15:14:29 UTC
The default amphora timeouts are too high for production environments.

The defaults today in OSP 13 are:
[haproxy_amphora] connection_max_retries = 300
[haproxy_amphora] build_active_retries = 300

Better defaults would be:

[haproxy_amphora]/connection_max_retries = 120
[haproxy_amphora]/build_active_retries = 120

Overriding these defaults should also be possible via Director parameters.

One other setting that should be possible to override via Director is [networking]/port_detach_timeout. The default value should not be changed for thee time being at least.

Comment 9 errata-xmlrpc 2020-03-10 11:18:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0760


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