Skip to content

fix: retry DynamoDB UnprocessedKeys and UnprocessedItems#44

Draft
hussein-awala wants to merge 1 commit intomainfrom
fix/dynamodb-unprocessed-items
Draft

fix: retry DynamoDB UnprocessedKeys and UnprocessedItems#44
hussein-awala wants to merge 1 commit intomainfrom
fix/dynamodb-unprocessed-items

Conversation

@hussein-awala
Copy link
Copy Markdown
Owner

Summary

  • batch_get_item may return UnprocessedKeys and batch_write_item may return UnprocessedItems when provisioned throughput is exceeded
  • Previously these were silently dropped, causing data loss under load
  • Both AsyncDynamoDbGetBatcher and AsyncDynamoDbWriteBatcher now retry in a loop until all items are processed
  • Added warning-level logging when retries occur

Test plan

  • Existing DynamoDB integration tests pass
  • Verify retry behavior under throttled conditions (manual or with mocked responses)

🤖 Generated with Claude Code

batch_get_item may return UnprocessedKeys and batch_write_item may
return UnprocessedItems when throughput is exceeded. Previously these
were silently dropped, causing data loss under load. Now both methods
retry in a loop until all items are processed.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant