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

Refactor daser, pruner and syncer to allow for lower pruning window than sampling window #517

Open
zvolin opened this issue Jan 21, 2025 · 0 comments
Labels
node Related to `lumina-node`

Comments

@zvolin
Copy link
Member

zvolin commented Jan 21, 2025

We should allow lumina to sample beyond pruning window but drop data as we receive it. This allows ensuring data availability for last 30 days but contributing in reconstruction only for last day.
Ideally syncer and daser should be kept in sync, so that syncer doesn't introduce huge storage usage spikes by syncing headers faster than daser can sample them and drop data

@zvolin zvolin added the node Related to `lumina-node` label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
node Related to `lumina-node`
Projects
None yet
Development

No branches or pull requests

1 participant