Does not scale down when one of the provisoned values is already at the low limit #237
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
added 2 commits
March 16, 2015 09:16
…ers value When always-decrease-rw-together is true if either one is at the lower limit it will not scale down the other.
…r limit it will not scale down the other value. this should also work for secondary indexes
|
Thanks for the PR @lcabral37. I have merged and released it in version 1.20.4 now. |
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.
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?!