Balancing NGINX reverse proxy

Alex Samad alex at
Thu Mar 2 22:06:04 UTC 2017


if I am reading this right, you currently have too much load on 1 nginx
server and you wish to releave this by adding another nginx server in front
of it ?

What I have is 2 nodes, but I use pacemaker instead of keepalive - i like
it as a better solution - but thats for another thread.

what you can do with pacemaker is have 1 ip address distributed between
multiple machines - up to 16 nodes I think from memory.

It uses linux iptables module for doing this. It is dependant on the source
ip's being distributed, if there are clamp together the hashing algo will
not make it any better.

How many requests are you getting to overload nginx - i thought it was able
to handle very large amounts ?

are your nodes big enough do you need more CPU's or memory or ??


On 3 March 2017 at 01:40, polder_trash <nginx-forum at> wrote:

> Hi,
> I have been reading the documentation and also searching this forum for a
> while, but could not find an answer to my question.
> Currently, I have a 2 NGINX nodes acting as a reverse proxy (in a failover
> setup using keepalived). The revproxy injects an authentication header, for
> an online website (transport is https).
> As the number of users grows, the load on the current machine starts to get
> uncomfortably high and I would like to be able to spread the load over both
> nodes.
> What would be the best way to set this up?
> I already tried adding both IP addresses to the DNS. But this, rather
> predictably, only sent a handful of users to the secondary node.
> I now plan about setting up an NGINX node in front of these revproxy nodes,
> acting as a round-robin load balancer. Will this work? Given the fact that
> traffic is over HTTPS, terminating the request will probably put all the
> load on the load balancer and therefore does not solve my issue.
> Your advice and help is greatly appreciated.
> Posted at Nginx Forum:
> php?2,272713,272713#msg-272713
> _______________________________________________
> nginx mailing list
> nginx at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx mailing list