Bug 995004

Summary:	maxconn set to 2 for local gear
Product:	OpenShift Container Platform	Reporter:	Jim Minter <jminter>
Component:	Containers	Assignee:	Brenton Leanhardt <bleanhar>
Status:	CLOSED ERRATA	QA Contact:	libra bugs <libra-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.2.0	CC:	baulakh, bleanhar, gpei, jialiu, libra-onpremise-devel
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openshift-origin-cartridge-haproxy-0.4.11-1.el6op.noarch	Doc Type:	Bug Fix
Doc Text:	The gear running HAProxy was limited to two connections, causing unexpected load distribution. This limitation has been removed in all new gears in the current release of OpenShift Enterprise. However, this fix will not be migrated to existing gears, so users must manually modify the haproxy/conf/haproxy.cfg file to implement this fix in their current gears.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-05 13:24:07 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:

Description Jim Minter 2013-08-08 11:55:16 UTC

The following commit in Origin appears to resolve the fact that with scaling gears the local gear only gets up to two connections.

https://github.com/openshift/origin-server/commit/5240cd5c6bafbd563aee2e2a078f9262e1e4d8f4

Is it feasible and appropriate for this to get into OSE 1.2?  The current functionality seems a bit odd.

Comment 2 Brenton Leanhardt 2013-08-08 13:40:52 UTC

*** Bug 995061 has been marked as a duplicate of this bug. ***

Comment 4 Gaoyun Pei 2013-08-13 07:49:47 UTC

Checked the code on puddle 1.2/2013-08-12.3.
All the code was merged in, so move this bug to VERIFIED.

Comment 7 errata-xmlrpc 2013-09-05 13:24:07 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.

http://rhn.redhat.com/errata/RHBA-2013-1211.html