Bug 1400030 - HAProxy scaling guidelines.
Summary: HAProxy scaling guidelines.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Jiří Mencák
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard: aos-scalability-34
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-30 10:19 UTC by Vladislav Walek
Modified: 2020-02-14 18:13 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 12:38:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Vladislav Walek 2016-11-30 10:19:55 UTC
Description of problem:

I want to just ask question, is there some guide how to scale the cluster based on input?
Like how big the cluster should be?

From customer:

"Please check the HAProxy for 400.000 parallel AMQPS connections (TCP based routing via sni headers) and also 400.000 parallel Web-Sockets HTTPS connections (Layer7).
Do you have information about how many connections this HAProxy in the master node could handle ?"

Thank you

Comment 3 Timothy St. Clair 2016-12-15 20:11:41 UTC
@Vladislav - 

There exists some data, but your initial question is vague, and your example is quite specific.  So I'm slightly confused by what you are looking for?  Could you please elaborate in more detail your specific request. 

xref: https://docs.openshift.org/latest/install_config/install/planning.html

Comment 6 Jeremy Eder 2016-12-19 13:47:57 UTC
Hi Vladislav,

As Tim said, haproxy scaling and performance tuning is in scope and underway.  Because it's a large area of research, we're taking a phased approach; making incremental progress with every minor release of OCP.

Jiri should reply soon to answer your last question about how many connections haproxy can handle in OCP.

The specific use-case for amqp and 400k connections I think is unfortunately outside of our current scope and ability to test.  That said, we will be continuing to push haproxy further and further as time goes on, and document architectural best-practices and tuning that is identified.

Comment 7 Vladislav Walek 2017-01-02 12:13:44 UTC
Hello Jeremy,

thank you for reply. Customer is closing the attach case, so you can close the ticket.
Thank you


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