-
Notifications
You must be signed in to change notification settings - Fork 0
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
[REPORT] Node panics with --trie-cache-size 0
#10
Comments
After block history import completes, node can still panic
|
Node kept panicking with |
--trie-cache-size 0
@yorickdowne are you using parity db ( I found a couple of substrate issues that might be relevant: Both were resolved fairly recently so are not yet merged into our code base. For now, the best I can suggest is to use a different value for trie cache size or leave it unset (which will use the default value).
|
I have not specified For now I am leaving |
Yes, I'd recommend setting |
Description:
During and after warp sync block history fill, the node panics. It then restarts and continues block (history) import.
This may be related to
--trie-cache-size 0
.Environment:
Operating System: Ubuntu 22.04
System Specification: OVH Adv-1
Version: chainflip-engine 0.8.7, chainflip-node 0.8.7
Logs:
The text was updated successfully, but these errors were encountered: