Well at least in my case, I can ask the application to make an orderly
reconnect. Where if nginx does it it just closes the connection.
The option to do it seems like better than having no option.
Alex
On 20 May 2017 at 21:11, B.R. via nginx wrote:
> ... and you would end up with connections
... and you would end up with connections serving different content (as per
different configuration) on the long run, leading potentially to an
increased number of problems.
How would you shut them down, if not gracefully?
If you want to keep long-lived connections open, do not make changes
server
Yes this exactly, I ended up been schooled by support :)
Seems like my understanding of graceful shutdown / reload ..
for the list and the archives
No keep alive for http1.0, has to be http1.1
client -> nginx keep alive session - these are shutdown once the current
request is completed
nginx
Hello!
On Fri, May 19, 2017 at 11:28:05AM +1000, Alex Samad wrote:
> Hi
>
> so I have lots of clients on long lived tcp connections , getting rp into 2
> back end app servers
>
> I had a line in my error log, saying one of the upstream was failed caused
> it timeout -
>
>
> then I got this
>
Hi
so I have lots of clients on long lived tcp connections , getting rp into 2
back end app servers
I had a line in my error log, saying one of the upstream was failed caused
it timeout -
then I got this
2017/05/18 13:30:42 [notice] 2662#2662: exiting
2017/05/18 13:30:42 [notice] 2662#2662: ex
