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

[Access] Add support for pebbleDB to execution data tracker/pruner #6260

Open
peterargue opened this issue Jul 25, 2024 · 1 comment · May be fixed by #6277
Open

[Access] Add support for pebbleDB to execution data tracker/pruner #6260

peterargue opened this issue Jul 25, 2024 · 1 comment · May be fixed by #6277
Assignees
Labels
Preserve Stale Bot repellent

Comments

@peterargue
Copy link
Contributor

peterargue commented Jul 25, 2024

Execution data tracker storage is currently stored in a BadgerV2 database. Reference.

Use pebble as the database for this storage. Split it out similarly to how we've done it for all the other storage interfaces (e.g., storage.Headers). Refactor the existing Badger storage implementation and add the Pebble version of the storage.

For example: storage.Headers

Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale Label used when marking an issue stale. label Oct 29, 2024
@franklywatson franklywatson added Preserve Stale Bot repellent and removed Stale Label used when marking an issue stale. labels Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Preserve Stale Bot repellent
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants