Repository navigation
[client] Add exponential backoff to lookup retries - #4970
Merged
Merged
Conversation
Contributor
Author
Jackeyzhe
reviewed
Nov 1, 2026
| | `client.lookup.retry-backoff` | `100 ms` | Duration | The initial delay before retrying a lookup that failed with a retriable error, such as `NOT_LEADER_OR_FOLLOWER`. The delay doubles with the lookup retry count and uses 20% jitter. Set to `0` to disable this backoff. | | ||
| | `client.lookup.retry-backoff-max` | `1 s` | Duration | The maximum retry delay. Must be between the initial backoff and `2147483647ms`. | | ||
|
|
||
| The retry backoff applies to each failed lookup and prefix lookup, preventing the client from |
Contributor
There was a problem hiding this comment.
nit: could we scope “each failed lookup” to retriable RPC response errors?
Member
There was a problem hiding this comment.
+1, though it's not only RPC response errors, lost connections and timeouts are backed off too
fresh-borzoni
approved these changes
Nov 2, 2026
Member
There was a problem hiding this comment.
@polyzos LGTM, thank you 👍
we should also handle this in rust, but it's for follow-up
Member
|
@fresh-borzoni, I would like to take this follow up for rust. |
Contributor
Author
|
@SteNicholas Sure, just open a ticket to track it 👍 |
1 of 2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #4959
Retriable lookup errors now back off exponentially instead of retrying immediately, and retry logging is one line per bucket batch.
client.lookup.retry-backoff(default100ms) andclient.lookup.retry-backoff-max(default1s), doubling with ±20% jitter, mirroringclient.writer.retry-backoff. Set to0to restore immediate retries. Historical-partition throttling keeps its own backoff, and new lookups aren't delayed by retries.Thread.sleepthat blocked client threads. This restores a delay between retries without blocking, using the deadline mechanism from [lookup] Support historical partition lookup for lake tables #3630.0backoff retries immediately, invalid settings are rejected.