store: add path field to StoreConfig
#6938
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add `path` field to StoreConfig which makes it possible to configure where RocksDB is located rather than hard-coding the location to `data` subdirectory. This helps with setup where neard home directory and the storage live on separate file systems. Previously such configurations required using of symbolic links or mounting storage inside neard home. Both of those solutions weren’t as clean as ability to point neard directly at the right place. This will become even more useful with planned cold storage which will call for all archival nodes to use multiple disks for the data (SSD for head data and HDD for archival data). Fixes: near#6857
matklad
approved these changes
Jun 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add
pathfield to StoreConfig which makes it possible to configurewhere RocksDB is located rather than hard-coding the location to
datasubdirectory. The directory can be set understore.pathJSONpath in
config.jsonfile, e.g.:This helps with setup where neard home directory and the storage live
on separate file systems. Previously such configurations required
using of symbolic links or mounting storage inside neard home. Both
of those solutions weren’t as clean as ability to point neard directly
at the right place.
This will become even more useful with planned cold storage which will
call for all archival nodes to use multiple disks for the data (SSD
for head data and HDD for archival data).
Fixes: #6857