Kinda like #137 but with the possibility of not scaling down writes (or not scaling them up).
Alternatively, just allow 0 as percentange in up and down as "i don't want to scale up/down"
also referring to #154.
I am using version 1.13
If I set "reads-lower-threshold" to 0 I got an error.
If I set "reads-lower-threshold" to 1 the script sometimes will perform autoscaling down.
Which workaround do you suggest me?
Yes, that's expected
What is decrease-reads-unit set to? DynamoDB should not allow you to perform a scale down at 1 unit, nor should Dynamic DynamoDB detect that a decrease is needed if this option is set to units.
I am currently using "decrease-reads-unit: percent"
So, using "decrease-reads-unit: unit" would solve my issue?
Thank you for your support
Well, not really. The functionality you are talking about is not implemented (this issue is about writing that function).
If you set
You will not get then behaviour you described ("* If I set "reads-lower-threshold" to 1 the script sometimes will perform autoscaling down*"). But it will only tell Dynamic DynamoDB that 1 is the lowest amount of reads that you will ever want to have. That you got decreases when having reads-lower-threshold set to percent is expected as DynamoDB allows you to set limits <1% of the total provisioning.
May be I could use "--run-once" and "num-read-checks-before-scale-down: 2".
This should completely avoid down scaling, because on each new run of the script the counter will be reset to 0, so it's impossible that it will arrive to 2. Correct?
Seems reasonable, give it a try.
Implemented controls for enabling up/downscaling #147
Added scaling controls to example config #147
Changed from "disable" to "enable" #147
Better config file consistancy
Removed deprecated scaling control #147
This has now been implemented. Further testing needed before release. The new controls will be called:
I have scheduled this for release in 1.18.0 which will be released during this week.