rocksdb
rocksdb copied to clipboard
Feature Request: Graceful upgrade
Is there any plans to add support for graceful upgrades? For example, I have a rocksb instance running on some server (and don't have replication or anything like that since each server has different local content). I need to upgrade my service that uses rocksdb. Typically, with my other services not using rocksdb, I would spin up another process running the new version of my application and have that process serve new traffic while the old process is finishing up serving the existing traffic and then the old process can shutdown. However, we can't open rocksdb in read/write mode from multiple processes so this approach of graceful upgrade doesn't work. Is there a way to make this work? Or maybe a way to reduce the time it takes for rocksdb to startup during this upgrade process so that it starts up much faster