Database Reference
In-Depth Information
Client-side error with status code 400 - retry
possible
The client-side errors that we have seen so far will always result in errors irrespective of
how many times we try (unless we debug the request). We will now see the errors that will
occur only in a certain period of time. So if we retry it, it might work on the consecutive
retry.
ProvisionedThroughputExceededException
This is a usual exception that occurs when too many clients are providing too many re-
quests for a larger table simultaneously, thereby exceeding the specified throughput capa-
city. In the case of this error, we need to wait for a while and retry. If we use the SDK, it
will take care of retrying, but in the REST request, the user has to take care of this.
ItemCollectionSizeLimitExceededException
This error will provide the Collection size exceeded error message. We have
already come across this case in the data model and the secondary index. I will answer this
case with a question. As we are already aware that a group of items that have the same hash
key cannot exceed 10 GB in size, if the insertion of a new item breaks this limit, then what
would happen? This exception will be thrown.
ThrottlingException
This exception will be raised if too many requests are submitted by the client rapidly and
will simultaneously result in a request spike. The error message shown by this error is
Rate of requests exceeds the allowed throughput . Since this error
comes under the retry possible error with status code 400, if we retry the same operation
after some time, we could get through.
UnrecognizedClientException
This error will provide the The Access Key ID or security token is in-
valid error message. This exception occurs if the access key ID or secret key is invalid.
Search WWH ::




Custom Search