ECS Service Discovery not respecting TTL when updating service
### Summary When updating a service or otherwise scaling out ECS tasks for a service that uses Service Discovery, tasks are being stopped before reaching the TTL of the service discovery record(s). ### Description When updating a service or otherwise scaling out ECS tasks for a service that uses Service Discovery, tasks are being stopped before reaching the TTL of the service discovery record(s). To reproduce - create an ECS service from a simple "hello world" type task definition that runs forever and does nothing. Set min healthy to 100, max to 200, count to 1. Setup service discovery and create a DNS record with a long TTL, say 300s. Update the service to use a new revision of the task definition (no changes to the task def needed), and note that the tasks are stopped before the TTL time is reached. ### Expected Behavior ECS Agent should remove the route53 record(s), and then wait to stop the tasks after the TTL duration has elapsed. ### Observed Behavior ECS Agent does not wait any additional time when stopping tasks for services that use service discovery. ### Environment Details ### Supporting Log Snippets
Posted by matthewduren on Oct 4, 2018, 6:39 PM
Tags
Related issues
- YouTube is blocking GIF comments from desktop (since 14 October 2026). Help wanted.
- > especially if given a few seconds of buffer.
- Claude Code does not respect the XDG Base Directory specification
- Most b2b gear will play well with a proxy server, and that will allow you to explicitly mitm everything going to the internet.
- [BUG] `npm install` started to hang on "still idealTree buildDeps" for 60 seconds if there are dependencies pointing to specific gitlab repository url (a regres
- "load metadata for" during docker pull hangs for about 10-20 seconds
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
onboarding (Network)
YouTube is blocking GIF comments from desktop (since 14 October 2026). Help wanted.
> especially if given a few seconds of buffer.
Claude Code does not respect the XDG Base Directory specification
Most b2b gear will play well with a proxy server, and that will allow you to explicitly mitm everything going to the internet.
[BUG] `npm install` started to hang on "still idealTree buildDeps" for 60 seconds if there are dependencies pointing to specific gitlab repository url (a regres
"load metadata for" during docker pull hangs for about 10-20 seconds
ECS Service Discovery not respecting TTL when updating service
ECS Service Discovery not respecting TTL when updating service
### Summary When updating a service or otherwise scaling out ECS tasks for a service that uses Service Discovery, tasks are being stopped before reaching the TTL of the service discovery record(s). ### Description When updating a service or otherwise scaling out ECS tasks for a service that uses Service Discovery, tasks are being stopped before reaching the TTL of the service discovery record(s). To reproduce - create an ECS service from a simple "hello world" type task definition that runs forever and does nothing. Set min healthy to 100, max to 200, count to 1. Setup service discovery and create a DNS record with a long TTL, say 300s. Update the service to use a new revision of the task definition (no changes to the task def needed), and note that the tasks are stopped before the TTL time is reached. ### Expected Behavior ECS Agent should remove the route53 record(s), and then wait to stop the tasks after the TTL duration has elapsed. ### Observed Behavior ECS Agent does not wait any additional time when stopping tasks for services that use service discovery. ### Environment Details ### Supporting Log Snippets
Comments (0)
No comments yet. Start the discussion.