fix(chainwatch): Make processor failures independent of each other #3254
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.
Chainwatch processor works in batches, collecting the deltas for each batch and shipping them off to sub-processing handlers which work through persisting the deltas to the DB. When any part of sub-processing fails, the
errgroup
cancels the whole batch. Instead, let's make each sub-process handler persist best-effort since they don't have schema dependencies between one another and log the failure. This should allow us to capture much more of our data despite internal state inconsistencies arising and making the whole thing bail.Also, reduce the batch size. Smaller batches means a less efficient catchup when chainwatch lags, but the trade off is smaller gaps in data on failures.