Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1190776

Summary:	tcp: implement tcp-ut bind option to set TCP_USER_TIMEOUT
Product:	Red Hat Enterprise Linux 7	Reporter:	John Eckersberg <jeckersb>
Component:	haproxy	Assignee:	Ryan O'Hara <rohara>
Status:	CLOSED ERRATA	QA Contact:	Brandon Perkins <bperkins>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.0	CC:	dmaley, nbarcet, rhos-flags
Target Milestone:	rc	Keywords:	ZStream
Target Release:	7.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	haproxy-1.5.4-5.el7	Doc Type:	Bug Fix
Doc Text:	Previously, some clients' connections using the Virtual IP (VIP) listened for messages but did not perform any write operation, and therefore the connections still appeared active from the perspective of haproxy even after the VIP failed. This update adds the "tcp-ut" option to haproxy for setting the Transmission Control Protocol (TCP) user timeout for faster failure detection on the front end, and the applications connected to haproxy now behave as expected.	Story Points:	---
Clone Of:
Clones:	1190783 1194407 1198791 (view as bug list)		Environment:
Last Closed:	2015-11-19 12:09:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1189241
Bug Blocks:	1175685, 1190783, 1194407, 1198791

Description John Eckersberg 2015-02-09 15:46:43 UTC

Need to grab this patch:

http://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=2af207a5f5e853

for faster failure detection on the frontend.  Primarily this helps in the case of VIP failover, where writes to the frontend get queued for retransmit for a very long time (tens of minutes) and the connection still appears active from haproxy's perspective.

Comment 1 Ryan O'Hara 2015-02-09 15:51:43 UTC

Patch from Willy can be found here:

http://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=2af207a5f5e853

Comment 10 errata-xmlrpc 2015-11-19 12:09:21 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://rhn.redhat.com/errata/RHBA-2015-2376.html