Scaling policy #9401
Closed
Scaling policy #9401
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Size Change: 0 B Total Size: 742 kB ℹ️ View Unchanged
|
|
"This PR is stale because it has been open 30 days with no activity. Unless a comment is added or the “stale” label removed, this will be closed in 3 days" |
|
This PR was closed because it has been stalled for 3 days with no activity. |
ioannakok
force-pushed
the
mob/scaling
branch
from
1130fe2 to
ecb0ba0
Compare
To fix error: ``` Resource handler returned message: "Period must be 10, 30 or a multiple of 60 ```
|
Closing in favour of: #10127 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our current scaling policy
ELB/Latencymetric.minSizeof the ASG.Background
ELB/Latencydoes not work for target tracking. According to the docs: "Request latency can increase based on increasing utilization, but doesn't necessarily change proportionally."Latencyis anELBCloudWatch metric and we're moving away from ELB to ALB. ALB CloudWatch metrics do not haveLatencyso once we swap from ELB to ALB we will have to change the metric anyway.RequestCountPerTarget: "The average number of requests received by each target in a target group." (can be used with target tracking scaling)TargetResponseTime: "The time elapsed, in seconds, after the request leaves the load balancer until a response from the target is received." Worth noting the SLI DevX dashboard usesELB/LatencyandApplicationELB/TargetResponseTimeas equivalent metrics to calculate Latency and it looks like for the purposes of scaling they are equivalent. (can be used with step scaling)Next steps
UPDATED:
We're going to do the following (see also release plan)
It looks like we have the following options:using the current Simple Scaling Policy. Once that's done, change our scaling policy to Step scaling on. No scaling policy at this point. No traffic will be sent to the article app.ALB/TargetResponseTimeALB/TargetResponseTimeImplement Step Scaling onELB/Latencybefore we migrate from ELB to ALB. Once we migrate, we should change the metric toALB/TargetResponseTime.CPUUtilisationand / orRequestCountPerTarget.