News for hackers. Stuff that matters.

A comment on Socket Sharding in Nginx Release 1.9.1. Parent comment

Re:Socket Sharding in Nginx Release 1.9.1 by otterley on Wednesday June 03, 2015 @10:32AM (#9652812)
What happens during the reload case for nginx? At reload time, the previous-generation worker that bound to the socket with SO_REUSEPORT will need to close its listener, just like haproxy.
[ Parent | on HN ]
Re:Socket Sharding in Nginx Release 1.9.1 by caf on Wednesday June 03, 2015 @10:41AM (#9652891)
When reloading, nginx starts up a new set of workers and duplicates the sockets across to them with SCM_RIGHTS. None of the sockets is closed - only duplicate file descriptors.
[ Parent | on HN ]
Re:Socket Sharding in Nginx Release 1.9.1 by ArmTank on Wednesday June 03, 2015 @10:38AM (#9652865)
In nginx worker processes don't open and don't close sockets. They inherit them from the master process.
[ Parent | on HN ]
Re:Socket Sharding in Nginx Release 1.9.1 by CrLf on Wednesday June 03, 2015 @12:36PM (#9653830)
But isn't that what reuseport changes? Each worker opening it's own socket?
[ Parent | on HN ]
Re:Socket Sharding in Nginx Release 1.9.1 by ArmTank on Wednesday June 03, 2015 @01:02PM (#9654077)
No, they don't (and they can't, since they usually don't have such privileges). The master process opens all sockets for each worker process.
[ Parent | on HN ]