Thats what support have advised me, reload finished the current request and then closes the connection. No longer honors the long lived
Alex On 27 April 2017 at 19:21, shivramg94 <nginx-fo...@forum.nginx.org> wrote: > We have a persistent connection to Nginx on which we are issuing https > requests. Now when we do a reload, the persistent connections (the requests > which are already accepted) are failing as soon as the reload was issued. > Those connections are being dropped. Is this the expected behavior? > > In the Nginx documentation, it was mentioned that the older worker process > would continue to run untile they have served the accepted inflight > requests > and then would go down. But the actual behavior seems to be different as > the > persistent connections are being dropped as soon as a configuration reload > was issued. > > To add to the above question, while reload was in progress, i am trying to > establish a new connection and its not being established. Can't the new > worker processes which were spawned as a result of configuration reload, > straight away serve the incoming new connections? > > Posted at Nginx Forum: https://forum.nginx.org/read. > php?2,273904,273904#msg-273904 > > _______________________________________________ > nginx mailing list > nginx@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
