You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using linea chain, node falls into an infinite loop and fails to switch to block processing after finishing state sync.
The problem seems to be caused by the conditions needed to assume state is available and switch away from state sync in MultiSyncModeSelector. Block headers are downloaded up to head - 32 blocks (FastSyncLag), where head is the block number of our best peer. This sets the best suggested header, which is used as a pivot when setting target block for sync (state ranges and healing TreeSync). That means that at best, the synced state can be head - 32 blocks, but as the head and therefore best header move with the chain, it is almost impossible to have state == head - 32, which is one of the conditions needed to assume state is downloaded and finish StateSync phase.
Using linea chain, node falls into an infinite loop and fails to switch to block processing after finishing state sync.
The problem seems to be caused by the conditions needed to assume state is available and switch away from state sync in
MultiSyncModeSelector
. Block headers are downloaded up to head - 32 blocks (FastSyncLag
), where head is the block number of our best peer. This sets the best suggested header, which is used as a pivot when setting target block for sync (state ranges and healingTreeSync
). That means that at best, the synced state can be head - 32 blocks, but as the head and therefore best header move with the chain, it is almost impossible to have state == head - 32, which is one of the conditions needed to assume state is downloaded and finishStateSync
phase.Screenshots
The text was updated successfully, but these errors were encountered: