On Mon, Jul 27, 2020 at 01:47:44PM +0200, Lukas Tribus wrote: > On Mon, 27 Jul 2020 at 13:14, Willy Tarreau <[email protected]> wrote: > > > However on a unix domain socket like this we never had this issue in > > > the first place, as connection-reuse cannot be used on it by > > > definition, correct? > > > > No, it doesn't change anything. We consider the connection, the protocol > > family it uses is irrelevant. > > I don't know why, but I always wrongly assumed that a unix domain > socket can only be datagram sockets, while really it's up to the > application. And of course we use a stream sockets.
Probably because you've long being used to seeing dgram sockets for logging. There is something related to unix sockets though, which is that we can't as cleanly rebind them upon reload (there's a non-atomic unlink/rename step). So a high connection-rate workload will notice a few connection retries upon reloads. And IIRC for ABNS sockets it's a bit worse as it's not possible to rebind them in parallel so we're back to the good old mode where the new process signals the old one asking to temporarily unbind so that it can bind in turn. I don't know if FD-passing method works there :-/ Willy
