Jay Taylor's notes

back to listing index

load balancing - How to use thousands of backends in haproxy? Is the new map feature useful for this? - Stack Overflow

[web search]
Original source (stackoverflow.com)
Tags: configuration haproxy howto stackoverflow.com
Clipped on: 2024-07-29

The 2024 Developer Survey results are live! See the results
    1. Home
    2. Questions
    3. Staging Ground
    4. Tags
    6. Saves
    7. Users
    8. Companies
    9. Labs
    10. Jobs
    11. Discussions

    13. Communities for your favorite technologies. Explore all Collectives

  2. Teams

    Now available on Stack Overflow for Teams! AI features where you work: search, IDE, and chat.

    Learn more Explore Teams

  3. Looking for

Asked 10 years, 5 months ago
Viewed 9k times
10

I want to use haproxy as a proxy and load balancer for thousands of backends. So a request needs to be proxied to the correct backend depending on hostname and then load balanced within the backend. I am using haproxy-1.5dev21.

The config file looks like this :

frontend public
  bind :80
  mode http
  acl host1 hdr_reg(host) host1.com
  use_backend be_host1 if host1

  acl host4000 hdr_reg(host) host4000.com
  use_backend be_host4000 if host4000

backend be_host[n]
  server hostn_1
  server hostn_2

Problem is that I get an added latency of 30ms per request if there are 5000 hosts. And for 20k backends, haproxy takes long time to load, not to mention the disaster on latency per request.

Can I do something better than sequential acl rules? I have not found an example for the new map feature - the release notes say it can be used for massive redirect rules. I tried this :

use_backend %[hdr(host), map(host_to_backend_map.file)]

Something obviously stupid above in using maps, but any guidance would be helpful. Thanks!

asked Feb 25, 2014 at 20:26
rcrc
22122 silver badges1010 bronze badges

2 Answers

Sorted by:
12

Some shortcomings were removed from the config file after expert input, and I list them here in case anyone else may find it useful.

  1. Use hdr(Host) instead of hdr_reg(). This vastly improves the time consumed to evaluate the ACLs. Even better, avoid acl and use the inline evaluation e.g.

    use_backend host1 if { req.fhdr(host,1) -m str host1.domain.com }

  2. Use nbproc>1. In case of concurrent connections, this helps. Though it makes it difficult to debug.

  3. For the backends, use IP address directly instead of 'server hostn_1 dns_of_server:port_number'

  4. Put 'fullconn 1000' in the defaults section. This improves the load time immensely.

Finally, use the latest haproxy git checkout and observe the enhancement in load time. It has come down considerably. Its now order of seconds compared to minutes before.

Also, regarding the 'map' feature, a new dynamic use_backend scheme is in the works that should remove the need to write as many ACLs.

answered Mar 28, 2014 at 1:13
rcrc
22122 silver badges1010 bronze badges
1

I was having the same problem. I am currently experimenting with Nginx + Lua with all the backends stored on Redis.

Request flow looks as below.

  1. Request is received at Nginx.
  2. Based on the request host, Redis is queried. A Lua module is available for Redis.
  3. Backend info is retrieved from Redis and Nginx proxies the request to appropriate backend.
  4. Backend(HAProxy), then load balances the request.

Motivation for this is from http://openresty.org/#DynamicRoutingBasedOnRedis

Hope this helps.

answered Nov 19, 2014 at 6:58
sudhir
2144 bronze badges

Your Answer

Community wiki

Not the answer you're looking for? Browse other questions tagged or ask your own question.

Hot Network Questions