Backfill fixes #31
Merged
Backfill fixes #31
Conversation
This file contains 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
christophercampbell
force-pushed
the
backfill-updates
branch
2 times, most recently
from
aa81b2a
to
f04b47f
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
arnaubennassar
approved these changes
Nov 23, 2023
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.
This PR updates the data backfill to retrieve data from the trusted sequencer before trying the other data nodes. The sequencer tracker now tracks the URL changes as well as address changes of sequencer. The data is also now checked against it's expected hash before storing.
Deployments that have gaps in data can restart their data backfill by setting their L1 sync_tasks record to 0.
UPDATE data_node.sync_tasks SET block = 0 WHERE task = 'L1'