Skip to content

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

@j1010001

Description

@j1010001

Why (objective)

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 ? (Key results)

  • 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

Metadata

Metadata

Assignees

Labels

ExecutionCadence Execution Team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions