You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
275 items processed (98.58 items/sec)Error:
BatchWriteError(Service(ProvisionedThroughputExceeded("The level of configured provisioned throughput for the table was exceeded. Consider increasing your provisioning level with the UpdateTable API.")))
com.amazon.coral.availability#ThrottlingException\",\"message\":\"Throughput exceeds the current capacity of your table or index. DynamoDB is automatically scaling your table or index so please try again shortly. If exceptions persist, check if you have a hot key: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html\"}", headers: {"server": "Server", "date": "Mon, 26 Feb 2024 06:54:54 GMT", "content-type": "application/x-amz-json-1.0", "content-length": "367", "connection": "keep-alive", "x-amzn-requestid": ...
InternalServerError
[2024-02-26 18:27:57] Error: BatchWriteError(Service(InternalServerError("Internal server error")))
[2024-02-26 18:27:58] exit status 1
2024e41 51694aa
also allows retries for ThrottilingException and InternalServerError.
Ideally, it would be better to consider retry for all of the following retrievable exceptions.
An error occurred when executing dy import.
AWS guidelines recommend retries with Exponential Backoff.
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html#Programming.Errors.BatchOperations
Therefore, in my project, I have forked this repository and added Exponential Backoff by backon.
Do you plan to add retry handling in the future?
The text was updated successfully, but these errors were encountered: