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
Hi, I am using the Swarm mode . I need to upgrade / downscale scale the service containers gracefully. That means I need the container to stop accepting new connections (= disable it on LB) and wait for all current connections to terminate. But, the stream of current connection has been break, that means the current request has not been handled successfully. After that the container can be stopped.
Steps to reproduce the issue:
docker swarm start with 2 nginx server container.
client send a keep-alive request to the server.
docker swarm update the server with the 'quit' signal. so the nginx server can stop gracefully.
but the stream of current connection is break by docker swarm.
Describe the results you received:
1.the current connection is not handled successfully, because the client can not get the successful result from the server, so the connection between client and server is keep alive. due to docker swarm's timeout mechanism, container is forced to stopped by the docker swarm with errcode 137.
Describe the results you expected:
the docker swarm can not break the stream of current connection in timeout's limit. swarm can stop new connection of client. I want update the container gracefully. so it means the server have to handle the request successfully and send the result to the client successfully.
Thank you, best regards.
Additional information you deem important (e.g. issue happens only occasionally):
I think this is a duplicate of #30321, which is currently being discussed; please subscribe to that issue to stay informed on updates. I'll go ahead and close this issue so that the conversation doesn't diverge, but feel free to comment after i closed
Description
Hi, I am using the Swarm mode . I need to upgrade / downscale scale the service containers gracefully. That means I need the container to stop accepting new connections (= disable it on LB) and wait for all current connections to terminate. But, the stream of current connection has been break, that means the current request has not been handled successfully. After that the container can be stopped.
Steps to reproduce the issue:
Describe the results you received:
1.the current connection is not handled successfully, because the client can not get the successful result from the server, so the connection between client and server is keep alive. due to docker swarm's timeout mechanism, container is forced to stopped by the docker swarm with errcode 137.
Describe the results you expected:
Thank you, best regards.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: