Open DmytroNazarenko opened 1 year ago
Reproduced on mainnet: skale-node: 3.0.0 skaled: 3.19.0
In the provided log, skaled shows first message related to catch-up after 9 minutes of work:
[2023-01-27 18:39:14.594] [14:catchup] [info] 0:CATCHUP_GOT_BLOCKS:COUNT:12968:STARTBLOCK:1
is this wrong? is there any limit on this time?
Versions Skaled: skalenetwork/schain:3.16.0-beta.6
Environment 20 active nodes on the network 8 schains up and running
Preconditions Load tests with blockchain-killer (1 GB of state in use)
Steps to Reproduce/Description
Expected behavior Skaled should start catching up blocks in 2-5 minutes after creation.
Actual result Skaled could not catchup blocks after 10-12 minutes of downtime and may be restarted by skale admin
skaled_not_catchup.log