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

Depending on network reliability and speed, the AMP deployment may fail #1630

Closed
ndegory opened this issue Aug 7, 2017 · 1 comment
Closed

Comments

@ndegory
Copy link
Contributor

ndegory commented Aug 7, 2017

The timeout definition in the AMP stack files (cluster/agent/stacks/) is based on the time spent between the service creation/update request and all tasks in the expected state. One significant part of this time is spent pulling the Docker image (when it's not already there), which brings a high variability depending on the host where it's running, depending on the performance of Docker Hub and depending on what has already been pulled.
Raising the timeout to excessively high values to avoid a Error: context deadline exceeded is not a satisfying solution, there should be a check on the status of the tasks to identify when the image has been pulled, to start waiting for the timeout.

@ndegory
Copy link
Contributor Author

ndegory commented Aug 7, 2017

PR #1628 seems to be broken because of this issue

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

1 participant