Skip to content

[client] Lookup sender need retry to send when leader not found in metadata cache#2052

Merged
wuchong merged 2 commits intoapache:mainfrom
swuferhong:lookup-retry-for-leader
Dec 1, 2025
Merged

[client] Lookup sender need retry to send when leader not found in metadata cache#2052
wuchong merged 2 commits intoapache:mainfrom
swuferhong:lookup-retry-for-leader

Conversation

@swuferhong
Copy link
Copy Markdown
Contributor

Purpose

Linked issue: close #2051

[client] Lookup sender need retry to send when leader not found in metadata cache

Brief change log

Tests

API and Format

Documentation

@swuferhong swuferhong force-pushed the lookup-retry-for-leader branch 2 times, most recently from 43e8974 to 3a0c7e4 Compare November 30, 2025 06:46
@swuferhong swuferhong force-pushed the lookup-retry-for-leader branch from 3a0c7e4 to 2f57cb3 Compare November 30, 2025 06:57
@swuferhong
Copy link
Copy Markdown
Contributor Author

@wuchong comments addressed.

@wuchong wuchong merged commit 8635169 into apache:main Dec 1, 2025
5 checks passed
@swuferhong swuferhong deleted the lookup-retry-for-leader branch December 18, 2025 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Lookup sender only retry 3 times for finding leader even if a large lookup retry count is configured

2 participants