Prevents scaling down write capacity as long as there are throttled w… #319
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.
…rite requests.
Please integrate this commit into the main project. It solves the following issue:
The dynamic DynamoDB scaler considers the used write capacity and the number of throttled writes when scaling up. This works fine.
But when scaling down it only considers the used write capacity - but ignores the throttled writes. This made the scaler scaling capacity up and down continuously when the used write capacity collapsed due to throttled writes.
So I added a little check that prevents it from scaling down as long as there are still throttled writes.
Cheers
Robert