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.
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