Hi,
I didn't subscribed to the list and noticed that there was several exchanges on this thread that I didn't read so far. To share a bit more of our context: * we do not reload every 2ms, this was the setting used to be able to reproduce easily and in a short period of time. Our reload average is more around 5 to 10s, which seems consistent to me on relatively big setups (I'm talking about 1 hundred of physical nodes per DC that makes run up to 1 thousand of app instances). * true, it's something that becomes very common as long as I/PaaS-style architectures are adopted. On our side we work with Apache Mesos and schedulers that add/remove backends as long as the end-user scale his application or if node/app fails, are under maintenance etc. By the way, I noticed that a lot of these "trending" projects are using HAProxy as their external load balancing stack (and most of them are also usually run over systemd-based distros), so it seems to me that this will fix some setups (that apparently rely on Yelp approach to 'safely restart' their haproxy - but induce latencies). Apart from that, we exchanged off-list with Willy about the submitted patch. It seems that if fixes the issue. I now have only one instance bound to the TCP sockets after the reloads, the others are there just to terminate the existing connections. Pierre
