(op-node) Keep consistent status when meet an unexpected el sync #222
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
krish-nr
force-pushed
the
pbss_recover_chore
branch
from
5e7ce6c to
0de1dc7
Compare
krish-nr
force-pushed
the
pbss_recover_chore
branch
from
0de1dc7 to
b9a212b
Compare
welkin22
reviewed
Aug 2, 2024
welkin22
reviewed
Aug 2, 2024
krish-nr
force-pushed
the
pbss_recover_chore
branch
from
5419a13 to
87b9c90
Compare
welkin22
reviewed
Aug 6, 2024
welkin22
reviewed
Aug 6, 2024
welkin22
reviewed
Aug 6, 2024
krish-nr
force-pushed
the
pbss_recover_chore
branch
from
379dccb to
ed8c9e8
Compare
krish-nr
force-pushed
the
pbss_recover_chore
branch
from
ed8c9e8 to
5ed6112
Compare
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
When op-geth meet an unexpected shutdown(OOM, forcekill, etc...) and the truncate operation results in the deletion of head data, the block-by-block insertion requests from op-node will trigger an EL sync in geth. This PR addresses this situation.
related geth change: https://github.com/bnb-chain/op-geth/pull/132
Rationale
When handling unexpected EL sync triggers, state synchronization is performed based on the specific errors returned by geth.
Example
N/A
Changes