Closed tac0turtle closed 3 years ago
This is a bug where snapshotting was configured to x and pruning was configured to y. It would be good to error out in the case where snapshotting is not happening on a multiple of pruning. this way you avoid getting to a hieght and erroring out
Do you think this could be state machine breaking, or is can it be safely back ported to v0.42.x ?
I thought we already added a check for this in BaseApp
? Not sure if its in 0.42. I could be wrong here, but I thought we added a check to make sure the snapshotting configuration takes into consideration the pruning configuration.
https://github.com/cosmos/cosmos-sdk/blob/master/baseapp/baseapp.go#L307-L318
ah then it should be backported.
This is actually already in v0.42.x: https://github.com/cosmos/cosmos-sdk/blob/release/v0.42.x/baseapp/baseapp.go#L296-L308
so this issue still needs more investigating
So can we close this?
Or at least @marbar3778 could you help us reproduce this? @likhita-809 on our side ran an osmosis node with pruning = "everything"
until ~17000 and still can't repro.
Or at least @marbar3778 could you help us reproduce this? @likhita-809 on our side ran an osmosis node with
pruning = "everything"
until ~17000 and still can't repro.
then it seems there is some non-determinism somewhere. I was able to reproduce it on two nodes. Will try again
@marbar3778 can you leave any comments on this?
@marbar3778 any progress on this ?
Or at least @marbar3778 could you help us reproduce this? @likhita-809 on our side ran an osmosis node with
pruning = "everything"
until ~17000 and still can't repro.then it seems there is some non-determinism somewhere. I was able to reproduce it on two nodes. Will try again
@marbar3778 did you try this again ?
trying to connect to nodes now
I wasnt able to reproduce, super weird. Will close for now
Summary of Bug
Node tried to prune with an active reader, this should not be possible
Version
0.42.5
Steps to Reproduce
you can reproduce by syncing an osmosis node with pruning set to everything.
logs:
cc @ValarDragon @sunnya97 not sure if this coming from one of your modules but should make note in a README.
For Admin Use