You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From my understand, transfer will send fd to new process, let next process continue to drain connections in that fd's backlog.
but If new process use REUSEPORT and then listen, accept, it still can accept connections from kernel socket addr 4 tuple.
Why we need transfer not create?
The text was updated successfully, but these errors were encountered:
Good question. Sockets under REUSEPORT have their own listening queues. When closing such a socket (in the old process), all the half-opened TCP connections are dropped. To such connections, the server is offline.
When a listening socket is transferred. It still binds to the same listening queue that old socket binds to. So when the old socket is closed, no connection will be lost.
From my understand, transfer will send fd to new process, let next process continue to drain connections in that fd's backlog.
but If new process use REUSEPORT and then listen, accept, it still can accept connections from kernel socket addr 4 tuple.
Why we need transfer not create?
The text was updated successfully, but these errors were encountered: