-
Notifications
You must be signed in to change notification settings - Fork 137
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
BoltDB cannot state sync #235
Comments
I'm not sure I understand the connection between BoltDB using a single file format and the inability to state sync. The latter seems like the first thing to tackle. Are there an issue and/or some logs that could help us understand what's happening? |
oh, sure thing! Ok, so, currently we make everything as a folder. So like:
is a folder. In fact maybe I can fix that now. Bolt would like a file |
Is that behaviour specific to Osmosis? I ask, because as far as I know stock Tendermint doesn't create the database path directly—it creates the enclosing directory (e.g., If the host is creating the target path as well as the enclosing directory, then probably the simplest fix is to disable the Perhaps better would be to have the host not try to pre-create the target path. The tm-db backends all create their working directory anyway, so it's redundant (though harmless) to do it explicitly. And then BoltDB should work out of the box. (If it doesn't already, tm-db should probably require that the implementation be responsible for creating its own targets—Badger and LevelDB definitely already do, I am not sure about Rocks). I don't think it necessarily makes sense to delete the boltdb backend from tm-db just for this alone, though. |
thanks I will look into it next week :) |
Bolt stores everything as a single file (iirc)
So now we get:
Feedback needed, please let me know which direction to take:
The text was updated successfully, but these errors were encountered: