fix(indexer): guarantee projection idempotency for concurrent/out-of-order replays - #1439
Open
aurorabini wants to merge 1 commit into
Open
Conversation
…order replays Harden EventLog persistence against the P2002 race when two workers replay the same ledger range, and prove idempotency with an exhaustive test that processes every fixture event twice and asserts identical state, plus concurrent-replay and out-of-order delivery coverage. Closes Akanimoh12#1260
|
@aurorabini Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
1 participant
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.
Summary
Guarantees indexer projection idempotency (issue #1260). PRs, backfill (#1259), and other recovery paths depend on this.
persistEventLognow treats aP2002unique-constraint violation (txHash, topic, ledger) as a replay instead of propagating — so two workers processing the same ledger range concurrently can't double-count.tests/idempotency.test.tsprocesses every fixture event twice and asserts identical aggregate state across all projection tables (Tip,Refund,User,Goal,Subscription,CreditScore,CreditScoreHistory,EventLog).Promise.allleave exactly one row per event.Closes #1260