aws / aws/containers-roadmap

[ECS] [request]: Seperate scale out cool down from scale in cooldown

Open
#290 2 comments 0 reactions 0 assignees View on GitHub
ECS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

**Tell us about your request**
Scale out cool down should be different than scale in cool down and the values must not be the same. Also the cool down should only apply to scaling into the same direction. At least scaling out should happen immediately even when a scale down cool down period is still active.

**Which service(s) is this request for?**
Fargate, ECS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Currently we have the problem that a cluster which is scaling in and is in cooldown can not scale out immediately when request traffic is increasing at that time. This can lead to a dead period that is as long as the cool down.

**Are you currently working around this issue?**
Not scaling in basically, which is expensive to operate

**Additional context**
none

**Attachments**
none

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified in the issue. Start by reviewing the ECS and Fargate service behavior around scale-in and scale-out cooldowns; done means separate directional cooldown values and immediate scale-out while a scale-in cooldown is active.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.