A partial outage plus aggressive client retries turns into DynamoDB throttling across the fleet. What contributing cause should developers address?
Select an answer to reveal the explanation.
Short Explanation
Hammering retries during a blip can turn a limp into a DynamoDB stampede. Back off with jitter so the SDK is not the amplifier making throttling worse.
Full Explanation
Aggressive client retries without suitable backoff can multiply load during partial failure and induce or worsen DynamoDB throttling. Adjusting retry limits, exponential backoff, and jitter reduces retry storms. Disabling backoff, hiding metrics, or switching to heavy consistent scans increases pressure instead.