Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker swarm update the container gracefully #31174

Closed
Renekton opened this issue Feb 20, 2017 · 1 comment
Closed

Docker swarm update the container gracefully #31174

Renekton opened this issue Feb 20, 2017 · 1 comment

Comments

@Renekton
Copy link

Renekton commented Feb 20, 2017

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:

  1. docker swarm start with 2 nginx server container.
  2. client send a keep-alive request to the server.
  3. docker swarm update the server with the 'quit' signal. so the nginx server can stop gracefully.
  4. 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:

  1. 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):

Output of docker version:

(paste your output here)

Output of docker info:

(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):

@thaJeztah
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants