aws / aws/containers-roadmap

Dynamically update ECS_RESERVED_MEMORY?

Open
#203 5 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

Hi Team,

Currently, the only way to "block out" memory external to ECS-scheduled containers (e.g. consumed by a TMPFS volume, or by a container scheduled directly through "docker run"), seems to be to specify a certain amount in advance via `ECS_RESERVED_MEMORY`. If this amount needs to change dynamically, we have to modify it in `ecs.config`, de-register that instance, and then register it again. That seems like a pretty disruptive change, especially that some tasks may still be running and would not normally be expected to fail or lost track of.

Or is there currently a way (or at least a workaround) to _dynamically_ update the amount of memory not managed by ECS, ideally through an API call, that doesn't disrupt existing tasks on that instance?

Thank you

Contributor guide

Open the contributing guide

Research direction

The issue mentions ECS_RESERVED_MEMORY, ecs.config, instance registration, and Docker containers, but names no source files or tests. Start by reviewing how ECS handles reserved memory and instance registration; done would mean defining a supported dynamic update or non-disruptive workaround, with its effect on running tasks documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, docker
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.