-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Can the desired target change during deployments? #174
Comments
Hi Josselin, thanks for sharing, it's always great to hear that the tool is helpful - highly appreciated! Normally what you describe should (🤞) not happen, as the Could you please share a few (simplified) examples of how you deploy (the commands you run) and describe how the "desired_target" (do you mean the "desired count" of the ECS service or another config option?) changes from before to after the deployment? Thanks |
Hello, Here is the kind of command we launch:
We are deploying multiple versions of our website and one of them uses a lot of instances (~150). We have issues with this one because our scaling mechanism seems to change the desired number of containers during the deployments and the tool does not seem to take it into account. Or maybe there is another issue but we reach the desired number of containers in the AWS console but the |
It seems to be a pagination issue because we use more than 100 instances, one of our SREs will propose a PR to fix it 😄 |
By the way, is it wanted not to allow having more instances than necessary to deploy ? Regarding this condition: https://github.com/fabfuel/ecs-deploy/blob/develop/ecs_deploy/ecs.py#L1182. |
The `list_tasks` call was capped at 100 tasks, if your service had a desired superior of 100 the deployment would fail. Fix fabfuel#174 Signed-off-by: Adrien Fillon <[email protected]>
The `list_tasks` call was capped at 100 tasks, if your service had a desired superior of 100 the deployment would fail. Fix fabfuel#174 Signed-off-by: Adrien Fillon <[email protected]>
Hello,
First thank you for this great tool, it is really helpful 😀
We have some timeout issues recently when using it to deploy our website.
After investigation, it seems to be because the "desired_target" changes during the deployment because our auto scaling mechanism but the tool does not seem to take it into account.
We could disable the auto scaling during our deployments but there is a risk for our infrastructure in case of traffic pics.
Is it a known bahavior? If yes, what would be the complexity to make the tool manage that?
Regards,
Josselin
The text was updated successfully, but these errors were encountered: