I think the gold standard for graceful restarts is nginx - it will start a
new instance (could be a new binary), send the accept fd's to the new
instance, then the original instance will stop accepting new requests and
allow the existing connections to drain off. The whole process is
controlled by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/04/2015 07:24 ??, Joseph Lynch wrote:
> Hello,
>
> I published an article today on Yelp's engineering blog
> (http://engineeringblog.yelp.com/2015/04/true-zero-downtime-haproxy-re
loads.html)
>
>
that shows a technique we use for low latenc
Hi David,
On Mon, Apr 13, 2015 at 12:53 PM, David Birdsong
wrote:
> I'm curious, did you weight the costs of simply converting your proxies to
> run on one of the BSD's? As I understand it, their implementation of
> SO_REUSEPORT would mean zero downtime reloads just work as
> hoped-for/expected.
Wow, this is a really informative blog post. Thanks for sharing!
I'm curious, did you weight the costs of simply converting your proxies to
run on one of the BSD's? As I understand it, their implementation of
SO_REUSEPORT would mean zero downtime reloads just work as
hoped-for/expected.
On Mon, A
Thanks for sharing this. This is a great and useful article!
Hello,
I published an article today on Yelp's engineering blog (
http://engineeringblog.yelp.com/2015/04/true-zero-downtime-haproxy-reloads.html)
that shows a technique we use for low latency, zero downtime restarts of
HAProxy. This solves the "when I restart HAProxy some of my clients get
RSTs" p
6 matches
Mail list logo