application pruning not working as expected

[omritoptix]

$ rollappd version
v2.2.0-hotfix.3

even though pruning seems to be working with these settings applied:

/usr/local/bin/rollappd start --log_level debug --pruning=custom  --pruning-keep-recent=100 --pruning-interval=10 --min-retain-blocks=10000

application db size doesn't change over time

du -sh ~/.rollapp_evm/data/application.db/

656G    /home/ubuntu/.rollapp_evm/data/application.db/

also, the expected behaviour is that since the starting blocks are already pruned, queries at old height shouldn't return any result, in reality they do:

$ rollappd q staking validators --height 1
pagination:
  next_key: null
  total: "0"
validators:
- commission:
    commission_rates:
...

the unknowns

• node isn't completely synced with the sequencer, hence the syncing speed might be roughly the same as pruning speed and the db size doesn't change ( doesn't explain why the query at old heights return values )
  • the application db size does go down when the process is being restarted

[mtsitrin]

few cents while debugging this issue:

• store logs (which includes pruning logs) are disabled in the cosmos-sdk by default

  func NewCommitMultiStore(db dbm.DB) types.CommitMultiStore {
  return rootmulti.NewStore(db, log.NewNopLogger())
  }

• seems like rollappd did prune since some height

  rollappd q staking validators --height 6872279
  Error: rpc error: code = InvalidArgument desc = failed to load state at height 6872279; version mismatch on immutable IAVL tree; version does not exist. Version has either been pruned, or is for a future block height (latest height: 6873360): invalid request

• I think that pruning-interval = "10" is way too low and causes a lot of overhead. Checking it now

[omritoptix]

closing as works as expected (we just didn't know what expected means here)