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
Deployments spend 4 extra minutes after new hosts are running and old hosts are gone.
Note here that by 177s, all the new hosts are running and the old task has no hosts, but the deployment stays open with DRAINING.
Details:
Here's the manifest:
name: web
type: Load Balanced Web Service
# Distribute traffic to your service.
http:
# Requests to this path will be forwarded to your service.
# To match all requests you can use the "/" path.
path: '/'
# You can specify a custom health check path. The default is "/".
healthcheck:
interval: 5s
path: '/'
port: 8080
healthy_threshold: 3
unhealthy_threshold: 2
timeout: 3s
grace_period: 60s
deregistration_delay: 30s
Observed result:
Deployments take twice as long.
Expected result:
I expect the hosts in the old task to live no longer than 30s before the deployment is marked complete.
Debugging:
I've set deregistration_delay, I've tuned healthcheck settings.
The text was updated successfully, but these errors were encountered:
Description:
Deployments spend 4 extra minutes after new hosts are running and old hosts are gone.
Note here that by 177s, all the new hosts are running and the old task has no hosts, but the deployment stays open with DRAINING.
Details:
Here's the manifest:
Observed result:
Deployments take twice as long.
Expected result:
I expect the hosts in the old task to live no longer than 30s before the deployment is marked complete.
Debugging:
I've set
deregistration_delay
, I've tunedhealthcheck
settings.The text was updated successfully, but these errors were encountered: