tiered storage in RocksDB #1
Description
Hello,
I'm looking into implementing tiered storage in RocksDB and have a couple of observations I'd like to clarify.
It seems there are a few ways to approach this:
Using the temperature property: My impression is that this feature may not be fully production-ready yet.
Using the db_path option: This seems straightforward, but it appears to be rarely used for tiered storage. I'm curious if there are specific drawbacks or limitations that explain its low adoption.
Modifying the RocksDB kernel: I have seen this approach successfully used in production, though it is obviously more involved.
I'm trying to understand the trade-offs here, especially why the db_path method isn't more common. Any insights would be greatly appreciated.
Thanks!