SYMC: LBaaS Haproxy default config limits the maxconn to 4K
Bug #1433768 reported by
Varun Lodaya
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juniper Openstack |
New
|
Medium
|
Rudra Rugge | ||
| OpenContrail |
New
|
Medium
|
Rudra Rugge | ||
Bug Description
LBaaS Haproxy defaults limit the max-conn to the VIP to 4K. Also the default max file-handles for the process are around 4K. This does not let us scale out the application sitting behind Haproxy.
We should increase the limits to max system limits.
Also, by default, vrouter only spins 1 Haproxy process, we could potentially increase the Haproxy processes to 2 or 4 which really increases the throughput. In 2.0, with availability zone concept being introduced in Contrail, we could essentially restrict Haproxy to specific nodes and use those nodes/hypervisors just as loadbalancers, thus letting us scale better.
| Changed in opencontrail: | |
| assignee: | nobody → Rudra Rugge (rudrarugge) |
| Changed in juniperopenstack: | |
| importance: | Undecided → Medium |
| Changed in opencontrail: | |
| importance: | Undecided → Medium |
| Changed in juniperopenstack: | |
| assignee: | nobody → Rudra Rugge (rudrarugge) |
| tags: | added: config lbaas |
| summary: |
- LBaaS Haproxy default config limits the maxconn to 4K + SYMC: LBaaS Haproxy default config limits the maxconn to 4K |
To post a comment you must log in.
