# Question about using the load balancer

**URL:** <https://www.ruby-forum.com/t/question-about-using-the-load-balancer/207170>\
**Category:** NGINX\
**Created:** [May 19, 2011, 9:35pm UTC](https://www.ruby-forum.com/t/question-about-using-the-load-balancer/207170 "2011-05-19T21:35:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![luislavena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/0ea827/32.png) [@luislavena](https://www.ruby-forum.com/u/luislavena)\
**Post date:** [May 19, 2011, 9:35pm UTC](https://www.ruby-forum.com/t/question-about-using-the-load-balancer/207170/1 "2011-05-19T21:35:29Z")

</div>

Hello,

I am using nginx as a load balancer in front of a tier of 4 web  
servers in a configuration very similar to:

[Simple Load Balancing | NGINX](http://wiki.nginx.org/LoadBalanceExample)

I am doing rolling deployments of my application on the 4 web servers.  
During a deploy, I take 2 of my 4 boxes out of the load balancer by  
switching to an alternative nginx configuration and running ‘nginx  
reload’. This has so far worked well.

One thing I noticed is that when I do this, nginx seems to snap  
(break) any connections that were open at the time of the reload. Is  
there a configuration setting that I could use to allow these  
connections to complete gracefuly, but otherwise have all new  
connections be handled according to the updated configuration?

Best Regards,

Kyle Burton

–  
Twitter: @kyleburton  
Blog: [http://asymmetrical-view.com/](http://asymmetrical-view.com/)  
Fun: [http://snapclean.me/](http://snapclean.me/)
