Skip to content

[v2.x] Resolve shard hash key range from the lease via ShardInfo - #1829

Merged
chenylee-aws merged 1 commit into
awslabs:v2.xfrom
chenylee-aws:backport-v2.x-retry-and-hashkey
Oct 26, 2026
Merged

chenylee-aws merged 1 commit into
awslabs:v2.xfrom
chenylee-aws:backport-v2.x-retry-and-hashkey

Conversation

@chenylee-aws

@chenylee-aws chenylee-aws commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Issue #, if available:

Description of changes:

Same change as #1828 on master. The shard's hash key range now comes from the lease (via ShardInfo) instead of a ListShards call. ListShards is used only as a fallback when trimming is enabled, and the result is cached.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@chenylee-aws
chenylee-aws marked this pull request as draft October 26, 2026 08:33
@chenylee-aws chenylee-aws changed the title [v2.x] Backport dispatch retry (#1822) and lease hash key range (#1828) [v2.x] Resolve shard hash key range from the lease via ShardInfo Oct 26, 2026
@chenylee-aws
chenylee-aws force-pushed the backport-v2.x-retry-and-hashkey branch from d4bda3d to d594eb9 Compare October 26, 2026 23:12
@chenylee-aws
chenylee-aws marked this pull request as ready for review October 26, 2026 23:14
@chenylee-aws
chenylee-aws merged commit 4e240d4 into awslabs:v2.x Oct 26, 2026
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.

2 participants