-
Notifications
You must be signed in to change notification settings - Fork 784
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
Flag --prune-blobs false prunes blobs older than 4096 epochs #5804
Comments
How long have you run the node with |
oldest_blob_slot is increasing
|
This is showing |
Yes, I'm trying different flags on the same server to solve the issue. In this case "blob_prune_margin_epochs" is quite high for blobs to be pruned and once I removed prune_blobs I haven't done any data clean up. |
I've checked and now I see that oldest_blob_slot is not increasing. Am I correct thats if I use checkpoint sync from scratch, it can backfill only blobs for 4096 latest epochs and from that moment blobs won't be pruned if I have prune_blobs: false? And the only way to backfill all blobs data is to sync from genesis? |
Yes that's correct. It will only backfill 4096 epochs from where you synced. Older blobs data can't be backfilled yet, We have an issue open for this: #5391 |
@nzenchik Has this issued been resolved? |
Yes, this particular issue has been solved |
Description
I'm running lighthouse with
--prune-blobs
set tofalse
, but blobs older than 4096 epochs are pruned. Here is args I used:I've also tried to add
--blob-prune-margin-epochs 1048576
but this doesn't help - blobs older 4096 are also prunnedHere is curl
"http://localhost:5052/lighthouse/database/info" | jq
resultVersion
sigp/lighthouse:v5.1.3
Expected Behaviour
With
--prune-blobs false
no blobs should be prunedThe text was updated successfully, but these errors were encountered: