Document how to catch a ProvisionedThroughputExceededException
See original GitHub issueThe documentation makes explicit references to a ProvisionedThroughputExceededException:
If a PutRecord request cannot be processed because of insufficient provisioned throughput on the shard involved in the request, PutRecord throws ProvisionedThroughputExceededException .
The link is broken, and there’s no information on how to catch this exception. Furthermore, grepping the source code for boto3
and botocore
only turns up documentation references to ProvisionedThroughputExceededException, no actual implementations of it, so I’m unsure what to import to try and catch/handle this exception.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:8
- Comments:12 (2 by maintainers)
Top Results From Across the Web
Error handling with DynamoDB - AWS Documentation
Discover the best practices for handling client and server errors and exceptions returned by Amazon DynamoDB operations.
Read more >Getting ProvisionedThroughputExceededException error ...
The read provisioned throughput is set to 1000 so it should be enough. The write provisioned t/p was set to a low value...
Read more >Developers - Document how to catch a ... - Bountysource
The documentation makes explicit references to a ProvisionedThroughputExceededException: If a PutRecord request cannot be processed because of ...
Read more >ProvisionedThroughputExceede...
DocumentationProvisionedThroughputExceededException ... The request rate for the stream is too high, or the requested data is too large for the available ...
Read more >Textract Throttling | AWS re:Post
So I just had my get document text increased to 35 but they kept ... I still get: An error occurred (ProvisionedThroughputExceededException) when...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This gist might be useful. h/t @shentonfreude
I was able to reproduce this by flooding a table with capacity=1 with write requests and capturing the error object. For future reference, here are what I think are likely the interesting bits: