[Feat] Facilitate RocksDB's secondary instances#3014
[Feat] Facilitate RocksDB's secondary instances#3014ljedrz wants to merge 3 commits intoProvableHQ:stagingfrom
Conversation
Signed-off-by: ljedrz <ljedrz@users.noreply.github.com>
Signed-off-by: ljedrz <ljedrz@users.noreply.github.com>
Very cool. Any evidence on how stable this is, or whether "read-only" instance historically had less bugs? |
It has been stable since at least 2021.
Compared to a read-only primary instance? I don't think either is any more stable, and I'm not sure if a read-only primary instance can be used while a primary read/write session is in progress. Secondary instances are also better suited for continued use (via |
Signed-off-by: ljedrz <ljedrz@users.noreply.github.com>
|
The stability question reminded me that we're actually a bit behind in terms of the version of RocksDB we're using. I pushed a commit updating it to 0.24; I've also confirmed that snarkOS builds with it. |
|
Hmm, not sure why the CI jobs are failing with a In any case, an update isn't required for this feature; if I don't find a solution, I'll revert back to |
This PR enables support for RocksDB's secondary instances. This could be used by all sorts of tools that require an insight into the storage of a running node.
Filing as a draft, as it depends on a pending
aleo-stdPR.