we are using an SW loadbalancer but L3 (keepalived).
DNS round robin are not a load balancer :) if one node is done, some
connections will arrive the down host that's not the right way i think.
HTTP Proxy are an option but you make a bottleneck of your connection to
WAN because all
The given options (DNS, SW load balancer, and HW load balancer) are all things
I've seen people use in production Swift clusters.
As mentioned in another reply, DNSRR isn't really load balancing, but it can be
used if nothing else is available.
One thing to consider when choosing a load
I wanted to check and see what others are using in the case of a Swift
installation with multiple proxy servers for load balancing/distribution. Based
on my reading, the approaches used are DNS round robin, or SW load balancers
such as Pound, or HW load balancers. I am really
If you choose to use DNS round robin, you can set TTL small and use a
script/tool to continous check proxy nodes to reconfigure DNS record if one
proxy node goes down, and vice-versa.
If you choose to use SW load-balancer, I suggest HAProxy for performance
(many high-traffic websites use it) and
Mail list logo