Error: DynamoDB Auto Scaling Not Working
Answered by Rafal Wilinski
What's Causing This Error
After turning on auto-scaling, you may encounter situations where your read/write activities get throttled, and the scaling does not work as initially intended. This might happen when your work is not staying elevated for a long time. The provisional throughput is modified by DynamoDB auto-scaling only when the workload remains elevated or depressed for a few minutes.
Solution: Here's How To Resolve It
DynamoDB auto scaling creates CloudWatch alarms to trigger auto-scaling. So, ensure that you do not delete any of these alarms. If you delete them, auto-scaling will not function as you expect. If you accidentally deleted these alarms, you can disable and enable auto-scaling once again, which will recreate the CloudWatch alarms.
However, suppose your elevation or depression of workload is limited to a short time. In that case, auto-scaling will not work properly as it is not the best in handling short-duration activity spikes.
You can read more about auto-scaling issues and their resolution here.
Other Common DynamoDB Errors (with Solutions)
- dynamodb the parameter cannot be converted to a numeric value NaN
- 'dynamodb' object has no attribute 'table'
- DynamoDB Item Does Not Exist
- dynamodb docker unable to open database file
- DynamoDB Delete Method Not Working For The First Time
- dynamodb mapper save not persisting
- failed to list tables not authorized dynamodb
- dynamodb cannot read property '0' of undefined
- cannot find module 'dynamodb-doc'
- AWS CLI DynamoDB Error Parsing Parameter
- dynamodb list_append returns true but does not work
- ExpressionAttributeValues contains invalid value: One or more parameter values were invalid: An AttributeValue may not contain an empty string
- ImportError: No module named boto3 (DynamoDB)
- DynamoDB FilterExpression Not Working
- dynamodb list_append if_not_exists not working