A developer is receiving an intermittent ProvisionedThroughputExceededException error from an application that is based on Amazon DynamoDB. According to the Amazon CloudWatch metrics for the table, the application is not exceeding the provisioned throughput. What could be the cause of the issue?
DynamoDB distributes throughput across partitions based on the hash key. A hot partition (caused by high usage of a specific hash key) can result in a ProvisionedThroughputExceededException, even if overall usage is below the provisioned capacity.
Why Option B is Correct:
Partition-Level Limits: Each partition has a limit of 3,000 read capacity units or 1,000 write capacity units per second.
Hot Partition: Excessive use of a single hash key can overwhelm its partition.
Why Not Other Options:
Option A: DynamoDB storage size does not affect throughput.
Option C: Provisioned scaling operations are unrelated to throughput errors.
Option D: Sort keys do not impact partition-level throughput.
Currently there are no comments in this discussion, be the first to comment!