-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while syncing: RPC method engine_newPayloadV2 crashed: pebble: batch too large: >= 4.0GB #111
Comments
Sorry for late response. You can increate the limit of batch and the size with |
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:
Trying to sync again. |
Hey @northwestnodes-eric, sorry again for late response. |
@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 : (if
develop
)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?
The text was updated successfully, but these errors were encountered: