-
Notifications
You must be signed in to change notification settings - Fork 745
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
Backfill mistakenly stores blobs in the hot DB #5114
Comments
michaelsproul
changed the title
Backfilll blobs mistakenly stored in hot DB
Backfilll mistakenly stores blobs in the hot DB
Jan 23, 2024
Indeed running on Goerli with checkpoint sync shows the blobs in the hot DB:
|
michaelsproul
changed the title
Backfilll mistakenly stores blobs in the hot DB
Backfill mistakenly stores blobs in the hot DB
Jan 23, 2024
API queries return empty lists of blobs:
|
I went with the first option based on this thinking:
|
Fixed by #5119 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Blobs stored during backfill are being stored in the hot DB. This is wrong, as they should be in the dedicated
blobs_db
(see: #4892). Prior to that they should have been in thefreezer_db
, so this seems to have been messed up for a while.The incorrect code is:
lighthouse/beacon_node/beacon_chain/src/historical_blocks.rs
Lines 123 to 128 in 5851027
That batch is committed straight to the hot DB directly here:
lighthouse/beacon_node/beacon_chain/src/historical_blocks.rs
Line 202 in 5851027
There's no usage of
do_atomically_with_block_and_blobs_cache
, which would have handled the division of ops between the blobs DB and the hot DB.Version
Lighthouse v4.6.0-rc.0
Steps to resolve
This is reasonably involved to fix, we need to:
import_historical_block_batch
.do_atomically_with_block_and_blobs_cache
.The DB migration is required to fix up the databases of nodes on Goerli that were recently checkpoint synced and put the blobs in the wrong DB.
I think we should block the v4.6.0 release for Sepolia/Holesky until we at least have a fix for where the blocks are written. It's probably OK to do the schema migration later, as it will just affect some Goerli nodes. But the sooner we do it the better in some sense, as more data will accumulate.
The text was updated successfully, but these errors were encountered: