> On 12 Jun 2020, at 12:41, Jan Prachař <jan.prachar@gmail.com> wrote:
>
> Hello, I checked code at the nginx-quic repo and I can't see how the
> following problem is addressed.
>
> When nginx reloads config, new workers are created and they inhertis
> receiving sockets from the old workers. That means that the new workers
> will start processing packets of the quic connections of the old
> workers. But the new workers lack context for them, so they will ignore
> the packets and quic connection will timeout, right?

Correct.

> A similar problem exists when a binary is changed.
>
> Do I miss something or will it be solved in the future?

This could be handled by a combination of CONNECTION_CLOSE
in old workers and Stateless Reset in new workers.

--
Sergey Kandaurov

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel