- Newest
- Most votes
- Most comments
Hello.
Not sure if it is usual to have a task pending for more than an hour.
There may be a problem with the network settings such as the subnet used by ECS.
How about checking the following documents and troubleshooting?
https://repost.aws/knowledge-center/ecs-fargate-tasks-pending-state
There could be multiple reasons to see this behavior :
-
Verify that your task definition is not seeking more resources (cpu, memory etc.) than what the container instance can offer. This could lead to insufficient resources situation
-
Check for any task placement constraints that might be disallowing the task to be scheduled on the lone container instance you have in your setup as per https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html
-
I would also suggest to verify your task definition for any syntax errors or missing any mandatory parameters.
-
Would also suggest to check the desired count and deployment configuration for your ecs service to ensure it meets the task demands. https://docs.aws.amazon.com/codedeploy/latest/userguide/deployment-configurations.html#deployment-configuration-ecs
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked a year ago
- Accepted Answerasked 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 days ago
Are you using Fargate or EC2? After the timeout (which would be around 15 min, not 1 hour), what is the error showing on the Task?