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

Does not scale down when one of the provisoned values is already at the low limit #237

Merged
merged 2 commits into from Mar 17, 2015

Conversation

Projects
None yet
2 participants
@lcabral37
Contributor

lcabral37 commented Mar 16, 2015

When always-decrease-rw-together is true if either one is at the lower limit it will not scale down the other value.

Ex. Writes is already at lower specified limit 5; reads is at 13 but can be lowered to 5 (its bellow the threshould)

The application keeps logging the message "Changing provisioning to 7 read units and 5 write units" but later logs "Reads could be decreased, but we are waiting for writes to get lower than the threshold before scaling down" instead of scaling down"

We need to scale down in this condition!

This looks related to #133 & #142?!

lcabral37 added some commits Mar 16, 2015

still return when one of the provisioned values is already at the low…
…ers value

When always-decrease-rw-together is true if either one is at the lower
limit it will not scale down the other.
When always-decrease-rw-together is true if either one is at the lowe…
…r limit it will not scale down the other value.

this should also work for secondary indexes

@sebdah sebdah merged commit 567cc00 into sebdah:master Mar 17, 2015

@sebdah

This comment has been minimized.

Owner

sebdah commented Mar 17, 2015

Thanks for the PR @lcabral37. I have merged and released it in version 1.20.4 now.

@sebdah sebdah self-assigned this Mar 17, 2015

@sebdah sebdah added this to the 1.20.x milestone Mar 17, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment