Neutron-LBaaS v2: mapping HAproxy process to cpu core

Bug #1650270 reported by Bartek Żurawski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
octavia
Invalid
Wishlist
Unassigned

Bug Description

HAproxy in default configuration is spawned on one CPU core. This could be changed by adding 'nbproc' option which provide possibility to chose how many cores should be used by HAproxy and which frontend/backend should use more than one core. That kind of configuration will provide better performance to load balancer.

Changed in neutron:
assignee: nobody → Bartek Żurawski (bartekzurawski1)
affects: neutron → octavia
tags: added: lbaas
Changed in octavia:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Michael Johnson (johnsom) wrote :

Hi Bartek,

With each release of haproxy we evaluate the improvements in the multi-process capabilities of HAProxy.
Enabling nbproc > 1 brings with it a number of caveats and features that are no longer available.
Examples include issues with the stats sockets/collection, issues with stick tables for session persistence, and issues doing non-disruptive configuration reload.

Currently, for HAProxy 1.6, nbproc > 1 is still highly discouraged as mentioned here in the documentation:
http://cbonte.github.io/haproxy-dconv/1.6/configuration.html#3.1-nbproc

So, based on advice we have received from folks at HAProxy technologies, we have been reluctant to enable multi-process mode by default.

We do understand some environments may benefit from using this setting. It is pretty straight forward to locally modify our jinja templates to enable multi-process mode for your deployment.

Revision history for this message
Bartek Żurawski (bartekzurawski1) wrote :

Hi Michael,

I just want to add it as an option because IMO it could help especially when there is big traffic that is going through LB. So by default HAproxy will be spawned in one thread (like it's now) but if you want you will be able to spawn it also with multi-process mode.

Changed in octavia:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron-lbaas (master)

Change abandoned by Michael Johnson (<email address hidden>) on branch: master
Review: https://review.openstack.org/415034
Reason: Abandoning this patch because it has been in merge conflict for four months without comment. Neutron-lbaas is also now deprecated and not accepting new features.

Revision history for this message
Gregory Thiemonge (gthiemonge) wrote : auto-abandon-script

Abandoned after re-enabling the Octavia launchpad.

Changed in octavia:
assignee: Bartek Żurawski (bartekzurawski1) → nobody
status: In Progress → Invalid
tags: added: auto-abandon
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.