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

Badger -> Pebble DB M2 - DB access refactoring for low-risk data (AN, EN, VN) #6527

Open
14 of 18 tasks
Tracked by #6939 ...
j1010001 opened this issue Oct 3, 2024 · 0 comments
Open
14 of 18 tasks
Tracked by #6939 ...
Assignees
Labels
Execution Cadence Execution Team

Comments

@j1010001
Copy link
Member

j1010001 commented Oct 3, 2024

Why

For top-level overview see Epic: #6515

Specifically for this issue:
Subset of Execution data gets indexed on ANs (events, Txs, Tx results, collections (meta object on top of Tx) ⇒ data that gets pulled out of execution data blobs).
ANs are the biggest data-heavy node after EN, expecting to grow further with EVM equivalence. By enabling data pruning we enable them to run AN with index on lower spec HW.
Most of this work is also relevant for VNs and because VNs are stateless we can cover it in this milestone as there is low risk of unintended consequences of DB operations.

Current status

How will we measure success ?

  • Data access is refactored for Access, Verification and Execution nodes.

DACI

Role Assigned
Driver Technical: @zhangchiqing , EM: @j1010001
Approver @Kay-Zee
Consulted @AlexHentschel, @franklywatson
Informed Flow protocol Engineering team

Tasks

Execution

Verification

Access

Tools

@vishalchangrani vishalchangrani added the Execution Cadence Execution Team label Dec 9, 2024
@j1010001 j1010001 changed the title Replace Badger with Pebble DB - Execution data Badger -> Pebble DB - Execution data Jan 15, 2025
@j1010001 j1010001 changed the title Badger -> Pebble DB - Execution data Badger -> Pebble DB M2 - DB access refactoring for low-risk data (AN, EN, VN) Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Execution Cadence Execution Team
Projects
None yet
Development

No branches or pull requests

3 participants