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

[Bug]: Deployments Spent 4 minutes after complete #5957

Open
iamnafets opened this issue Oct 22, 2024 · 0 comments
Open

[Bug]: Deployments Spent 4 minutes after complete #5957

iamnafets opened this issue Oct 22, 2024 · 0 comments
Labels
type/bug Issues that are bugs.

Comments

@iamnafets
Copy link

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.
image

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.

@iamnafets iamnafets added the type/bug Issues that are bugs. label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Issues that are bugs.
Projects
None yet
Development

No branches or pull requests

1 participant