Skip to content
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

storage/pruning: light node on mocha-4 is not pruning historical data #3195

Closed
Bidon15 opened this issue Feb 20, 2024 · 0 comments
Closed

storage/pruning: light node on mocha-4 is not pruning historical data #3195

Bidon15 opened this issue Feb 20, 2024 · 0 comments
Labels
bug Something isn't working external Issues created by non node team members

Comments

@Bidon15
Copy link
Member

Bidon15 commented Feb 20, 2024

Celestia Node version

v0.13.0

OS

macOS

Install tools

  1. clone repo
  2. checkout v0.12.4
  3. run binary
  4. checkout later at v0.13.0

Others

No response

Steps to reproduce it

  1. Install v0.12.4
  2. Initialise a da light node for mocha-4 testnet
  3. Sync to 1100000 block height
  4. Install v0.13.0
  5. Sync a v0.13.0 light node to the tip of the chain

Expected result

Pruning is done to historical blocks

Actual result

Pruning is not done for historical blocks. Light node is still storing past recency window data

Relevant log output

du -h ~/.celestia-light-mocha-4/
8.0K	/Users/bidon4/.celestia-light-mocha-4//keys/keyring-test
 16K	/Users/bidon4/.celestia-light-mocha-4//keys
 23G	/Users/bidon4/.celestia-light-mocha-4//data
 32G	/Users/bidon4/.celestia-light-mocha-4/

Notes

This is an acceptance test for users of da light nodes that are migrating from v0.12.4 to latest v0.13.0

@Bidon15 Bidon15 added the bug Something isn't working label Feb 20, 2024
@github-actions github-actions bot added the external Issues created by non node team members label Feb 20, 2024
@Bidon15 Bidon15 closed this as completed Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working external Issues created by non node team members
Projects
None yet
Development

No branches or pull requests

1 participant