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
Since the last couple of upgrades, I started receiving these two errors in the two different flavors. I am not sure why I will see a consensus failure sometimes and others it is just a panic.
I have found a resolution to me getting these errors. I normally run with pruning set to everything and then I maintain a min block count of unbonding time. When pruning is set to everything, I do not get more than 10 blocks in before the pebbledb issue presents itself in one way or another. With custom pruning set to an interval of 1000, I also still get the problem. But I have been able to avoid the problem with my pruning interval set to 3000.
It appears that smaller intervals for pruning are not being chunked properly for pebbledb, resulting in chunks over 4.0Gb for me.
Since the last couple of upgrades, I started receiving these two errors in the two different flavors. I am not sure why I will see a consensus failure sometimes and others it is just a panic.
I have found a resolution to me getting these errors. I normally run with pruning set to
everything
and then I maintain a min block count of unbonding time. When pruning is set to everything, I do not get more than 10 blocks in before the pebbledb issue presents itself in one way or another. With custom pruning set to an interval of1000
, I also still get the problem. But I have been able to avoid the problem with my pruning interval set to3000
.It appears that smaller intervals for pruning are not being chunked properly for pebbledb, resulting in chunks over 4.0Gb for me.
Panic error:
Consensus failure:
binary info:
uname -a
The text was updated successfully, but these errors were encountered: