Skip to content
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

Define Automatic scaling policy #24

Open
xmunoz opened this issue Dec 4, 2020 · 5 comments
Open

Define Automatic scaling policy #24

xmunoz opened this issue Dec 4, 2020 · 5 comments
Assignees

Comments

@xmunoz
Copy link
Contributor

xmunoz commented Dec 4, 2020

No description provided.

@cecilia-donnelly
Copy link
Member

"What are the conditions that should be met for us to turn this on?"

@xmunoz
Copy link
Contributor Author

xmunoz commented Dec 7, 2020

Determining the proper thresholds will require data from monitoring to determine how the machines handle load.

Helpful documentation for how to set up scaling policies: https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html

@xmunoz
Copy link
Contributor Author

xmunoz commented Dec 8, 2021

I think the scaling policy that we need will look at the number of messages in the various sqs queues, and use that to determine how much to scale. Unfortunately, this will require spinning up a new service that just reads and reports that data to Cloudwatch. That is what I will now be working on.

@xmunoz xmunoz self-assigned this Dec 8, 2021
@xmunoz
Copy link
Contributor Author

xmunoz commented Dec 8, 2021

@xmunoz
Copy link
Contributor Author

xmunoz commented Dec 21, 2021

After further discussions, it doesn't look I'll have time to implement this design. It would effectively require spinning up a new service (per-enviroment) that just watches the SQS queues (probably just HIGH_PRIORITY and VIDEO) and triggers a Cloudwatch alarm when the queue lengths get too long. The scaling group will then spin up new instances accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants