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

Problem: versionDB migration does not support pebbleDB #1236

Closed
GAtom22 opened this issue Nov 9, 2023 · 3 comments
Closed

Problem: versionDB migration does not support pebbleDB #1236

GAtom22 opened this issue Nov 9, 2023 · 3 comments

Comments

@GAtom22
Copy link

GAtom22 commented Nov 9, 2023

Describe the bug
At the moment, versionDB migration procedure does not support pebbleDB

~ $ evmosd changeset dump "/home/evmos/.evmosd/data_rocks" --home "/home/evmos/.evmosd/" --log_level "debug"
Error: unknown db_backend pebbledb, expected one of goleveldb,memdb,rocksdb

Would be great to add support for this DB

To Reproduce
Steps to reproduce the behavior:

  1. Start a node with pebbleDB.
    Usually this requires to replace the cometbft-db module
go mod edit -replace github.com/cometbft/cometbft-db=github.com/notional-labs/cometbft-db@pebble
go mod tidy
COSMOS_BUILD_OPTIONS=pebbledb make build
  1. Run a node with this config and store some data
  2. Perform the migration procedure to versionDB
@yihuang
Copy link
Collaborator

yihuang commented Nov 10, 2023

I think the dump cmd use the cometbft-db db opener as usual, maybe sth wrong with the cometbft-db replacement?

@GAtom22
Copy link
Author

GAtom22 commented Nov 10, 2023

will look into this, thanks!

@GAtom22
Copy link
Author

GAtom22 commented Jan 23, 2024

Closing because this issue is not related to versionDB, but related to the cometbft-db dependency

@GAtom22 GAtom22 closed this as completed Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants