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
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: