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.

Sign up for GitHub

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

Jump to bottom

feature(pruner/light)!: LNs should prune samples beyond availability window by default #3505

Open
renaynay opened this issue Jun 17, 2024 · 0 comments · May be fixed by #3912
Open

feature(pruner/light)!: LNs should prune samples beyond availability window by default #3505

renaynay opened this issue Jun 17, 2024 · 0 comments · May be fixed by #3912
Assignees
@renaynay
Labels
good first issue Good for newcomers v0.17.0 Intended for v0.17.0 release

Comments

@renaynay
Copy link
Member

Currently, LNs will only prune samples if --experimental-pruning is passed, but there's no reason for LNs to retain samples beyond availability window (30 days) as they only sample within that window anyway.

We should enable pruning for LNs by default.
@renaynay renaynay added the v0.16.0 Intended for v0.16.0 release label Jun 17, 2024
@renaynay renaynay self-assigned this Jun 17, 2024
@renaynay renaynay added v0.17.0 Intended for v0.17.0 release and removed v0.16.0 Intended for v0.16.0 release labels Sep 19, 2024
@renaynay renaynay added the good first issue Good for newcomers label Oct 2, 2024
This was referenced Oct 28, 2024
Draft
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@renaynay renaynay

Labels
good first issue Good for newcomers v0.17.0 Intended for v0.17.0 release
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

nodebuilder/pruner: Enforce light pruning renaynay/celestia-node
1 participant
@renaynay