-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
GoQuorum PANIC After Restart Post Enabling --privatetriecache.enable #1379
Comments
Hello, thank you for raising this. When we kill abruptly (SIGKILL) the state is not saved, so a reset will occur at the next restart. Here I propose a fix, I tested locally, but I think the node is kinda locked and need a restart to make a proper reset. Would you mind to test |
Thanks. Will test and revert |
@baptiste-b-pegasys Your test build ghcr.io/baptiste-b-pegasys/quorum:npe-private-state-cache seems to be on a wrong baseline version 1.9.23-stable-0f56bd31(quorum-v21.4.2) . As such it did not allow me to set the flag Incorrect Usage. flag provided but not defined: -privatetriecache.enable |
@frankie-lim-sweeho sorry I made a mistake somewhere. |
@baptiste-b-pegasys I have tested with the test build and confirmed it no longer panic are restart. Log attached incase u need. Thanks! |
GoQuorum Version: 22.1.1
Tessera Version: 22.1.0
Issue Description:
After enabling private trie cache by setting --privatetriecache.enable (#1353) , GoQuorum Geth will panic and crash consistently after 2nd restart. 1st time startup with --privatetriecache.enable works fine with transaction able to be perform.
Step to reproduce
Q-22.1.1-private-trie-cache-crash-4.log
Q-22.1.1-private-trie-cache-crash-3.log
Q-22.1.1-private-trie-cache-crash-2.log
Q-22.1.1-private-trie-cache-crash-1.log
The text was updated successfully, but these errors were encountered: