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
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Even with a large genesis block file, it should be able to sync the nodes properly.
Actual behavior
Procedure getHighestCommonBlock for given block ids returns the whole common block header, in case of testnet or mainnet genesis block header the size of genesis block header is too big (20-200MB).
When getting the block, it tries to decode the asset which takes long.
Genesis block are kept in memory
Steps to reproduce
Migrate 2.1.6 and generate genesis block (which is around 200MB)
Run lisk-core start -n mainnet with the new genesis block
Connect to running node as seed peer
Observer the syncing node fails to request block during synchronisation
Which version(s) does this affect? (Environment, OS, etc...)
5.1.1, 3.0.0
The text was updated successfully, but these errors were encountered:
Expected behavior
Even with a large genesis block file, it should be able to sync the nodes properly.
Actual behavior
getHighestCommonBlock
for given block ids returns the whole common block header, in case of testnet or mainnet genesis block header the size of genesis block header is too big (20-200MB).Steps to reproduce
lisk-core start -n mainnet
with the new genesis blockWhich version(s) does this affect? (Environment, OS, etc...)
5.1.1, 3.0.0
The text was updated successfully, but these errors were encountered: