title: Issue with Haproxy Reload
body: <p>We are using Haproxy on top of Mesos cluster, We are doing  dynamic reloads for Haproxy based on marathon events (50-100 times in a day). We have nearly 300 applications that are running on Mesos (300 virtual hosts in Haproxy). When we do dynamic reloads, Haproxy is taking long time to reload Haproxy, we observed that for 50 applications takes 30-40secs to reload Haproxy. We have a single config file for Haproxy, when we do reload all the applications are getting reloaded (Front-ends), this causing downtime of all applications. Is there anyway to reduce the downtime and impact on end-users.</p>
  
  <p>We tried this scenario,<br>
  <a href="http://engineeringblog.yelp.com/2015/04/true-zero-downtime-haproxy-reloads.html" rel="nofollow" title="true-zero-downtime-haproxy-reloads">"http://engineeringblog.yelp.com/2015/04/true-zero-downtime-haproxy-reloads.html"</a></p>
  
  <p>By this if user requests while reload, the requests are queued and serving after reload.</p>
  
  <p>But if we do multiple reloads one after another, HaProxy's old processes persist even after reloading the HaProxy service, this is causing serious issues.</p>
  
  <pre><code>root      7816  0.1  0.0  20024  3028 ?        Ss   03:52   0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -D -sf 6778
  root      7817  0.0  0.0  20024  3148 ?        Ss   03:52   0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -D -sf 6778
  </code></pre>
  
  <p><strong>Is there any solution stop the previous process once after it serving the request.</strong></p>
  
  <p><strong>Can we separate the configurations based on front-ends like in Nginx, so that only those apps will effect if there is any changes in backend.</strong></p>
  
  <p>Thank you.</p>