Open northwestnodes-eric opened 4 months ago
Sorry for late response. You can increate the limit of batch and the size with rpc.batch-request-limit
and rpc.batch-response-max-size
, respectively. BTW, did you try to sync Kroma mainnet? If you have issues not resolved, please leave any comments. I will respond to it. Thanks.
Hi @0xHansLee - we did indeed try to sync Kroma mainnet from scratch using the PebbleDB implementation. Trying again right now (currently at ~8mo) with the aforementioned flags set to 0 (indicating unlimited, AFAIK). I'll keep you posted.
Hi @0xHansLee the sync crashed with a different error this time. kroma-geth complained about the following:
kroma-geth | {"t":"2024-07-15T06:04:13.052137214Z","lvl":"eror","msg":"fail to resolve hash node","hash":"16028726...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:13.052339318Z","lvl":"eror","msg":"fail to resolve hash node","hash":"16028726...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:13.637616567Z","lvl":"eror","msg":"fail to resolve hash node","hash":"62538809...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:13.637850094Z","lvl":"eror","msg":"fail to resolve hash node","hash":"62538809...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:13.643579501Z","lvl":"eror","msg":"fail to resolve hash node","hash":"62538809...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:13.643801766Z","lvl":"eror","msg":"fail to resolve hash node","hash":"62538809...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:13.651338141Z","lvl":"eror","msg":"fail to resolve hash node","hash":"62538809...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:13.651395804Z","lvl":"eror","msg":"fail to resolve hash node","hash":"62538809...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:13.68728785Z","lvl":"eror","msg":"fail to resolve hash node","hash":"62538809...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:13.687504086Z","lvl":"eror","msg":"fail to resolve hash node","hash":"62538809...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:14.37603311Z","lvl":"eror","msg":"fail to resolve hash node","hash":"62538809...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:14.376260287Z","lvl":"eror","msg":"fail to resolve hash node","hash":"62538809...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:15.657100043Z","lvl":"eror","msg":"fail to resolve hash node","hash":"65514486...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:15.657361031Z","lvl":"eror","msg":"fail to resolve hash node","hash":"65514486...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:15.937945201Z","lvl":"eror","msg":"fail to resolve hash node","hash":"43145104...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:15.938187647Z","lvl":"eror","msg":"fail to resolve hash node","hash":"43145104...","err":"pebble: not found"}
kroma-geth | {"t":"2024-07-15T06:04:15.970086977Z","lvl":"eror","msg":"fail to resolve hash node","hash":"43145104...","err":"pebble: not found"}
Trying to sync again.
Hey @northwestnodes-eric, sorry again for late response. Could you try using our snapshot data? The url is https://snapshot.kroma.network/latest/snapshot.tar.gz.
@northwestnodes-eric if you are a full node? I also had the same problem,How did you solve it?
System information
Geth version:
geth version
CL client & version: lighthouse OS & Version: Linux Ubuntu 22.04 Commit hash : (ifdevelop
)Expected behaviour
Continuation of synchronization
Actual behaviour
Crash and burn. Even after disabling the
engine_
API namespace, synchronization crashes at this particular block.Steps to reproduce the behaviour
Sync a Kroma node from scratch, using the PebbleDB backend.
Backtrace
Is there any way to increase the allowed size? I do feel a batch size of >= 4.0GB is a bit hefty?