In the current synchronization mode, fastnode-type nodes fail to synchronize when a gap needs to be filled because elsync is not enabled by default. We have added a mechanism to trigger elsync in such scenarios.
Rationale
Added two configurations:
--fastnode=true(default is false)
--el-trigger.gap=86400 (default value)
These two configurations are not dependent on each other.
When fastnode is set to true, elsync will be automatically triggered every time fastnode starts.
In certain scenarios, where the block height is significantly lagging, we still want to enable elsync. In such cases, we can set el-trigger.gap to specify the lagging block height that triggers elsync. This configuration only takes effect when --syncmode=execution-layeris set.
Description
In the current synchronization mode, fastnode-type nodes fail to synchronize when a gap needs to be filled because elsync is not enabled by default. We have added a mechanism to trigger elsync in such scenarios.
Rationale
Added two configurations:
--fastnode=true(default is false)--el-trigger.gap=86400(default value) These two configurations are not dependent on each other. When fastnode is set to true, elsync will be automatically triggered every time fastnode starts. In certain scenarios, where the block height is significantly lagging, we still want to enable elsync. In such cases, we can setel-trigger.gapto specify the lagging block height that triggers elsync. This configuration only takes effect when--syncmode=execution-layeris set.Example
N/A
Changes
Notable changes: