Fix LogPoller reprocessing entire block range on partial failure#1465
Draft
Krish-vemula wants to merge 3 commits intodevelopfrom
Draft
Fix LogPoller reprocessing entire block range on partial failure#1465Krish-vemula wants to merge 3 commits intodevelopfrom
Krish-vemula wants to merge 3 commits intodevelopfrom
Conversation
Contributor
✅ API Diff Results - No breaking changes |
amit-momin
reviewed
Feb 24, 2026
amit-momin
reviewed
Feb 24, 2026
| return fmt.Errorf("failed processing block range [%d, %d]: %w", lastProcessedSlot+1, highestSlot, err) | ||
| } | ||
|
|
||
| lp.lastProcessedSlot = highestSlot |
Collaborator
There was a problem hiding this comment.
With the new lastProcessedSlot update logic, should we remove this from here?
|
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.


Description
Fixes excessive getBlock RPC calls caused by the LogPoller reprocessing already-succeeded blocks when a failure occurs partway through a block range. Previously, lastProcessedSlot was only updated after the entire range completed successfully any error (DB timeout, decoding failure, rate limiting) would cause the next tick to re-fetch and re-process every block from the start of the range. Now lastProcessedSlot advances incrementally after each successfully processed batch, so retries resume from where processing left off.