op-supernode: skip log backfill during CL sync#20960
Draft
karlfloersch wants to merge 1 commit into
Draft
Conversation
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
Skips interop log backfill whenever any configured supernode virtual node is running in consensus-layer sync mode. The configured backfill depth is left intact, but the effective depth passed into the interop activity is set to zero for CL-sync setups.
Motivation
During a fresh CL-sync recovery, SafeDB can have a startup boundary that is ahead of what the local EL has derived/imported. Cold-start log backfill then asks the local EL for blocks in that window and can pin interop startup on missing blocks. CL sync should be allowed to derive/import those blocks before interop validation advances.
Testing