- 
                Notifications
    
You must be signed in to change notification settings  - Fork 4.1k
 
Open
Description
We have nodes that:
- should prune to keep just the last 362,880 states (default pruning) and that, as well,
 - generate state-sync snapshots every 1,000 blocks, keeping the last 2 sets only.
 
Since only 2 sets of state-sync snapshots are kept, the nodes with this setup should never have snapshots older than 2,999 blocks. As the pruning is set to target states older than 362,880, this two settings should not overlap and the prune should be done normally.
The issue is that the nodes set like this are not pruning and are keeping all the states. This causes 2 issues:
- The disk usage grows more than expected, since those nodes are intended to prune.
 - If we eventually disable state-sync snap generation, they start tu aggressively prune, what causes CPU usage peaks above 80% for long time periods until the prune is complete. Additionally, the error 'ERR Error while pruning err="version does not exist" module=server' is registered every second on the log.
 
Were are using cosmos_sdk_version: v0.50.14.
Thanks in advance.
Metadata
Metadata
Assignees
Labels
No labels