You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the motivation or use case for the feature?
I don't need persistence for my use case. Restarting the whole keydb cluster can start without any data, but when a cluster node goes down (because of e.g. hardware failure) it should start as soon as possible and get the current data as soon as possible. This works better without persistent volumes.
Describe the solution you'd like
Using emptyDir storage instead.
The text was updated successfully, but these errors were encountered:
Collaboration and contributions are always welcome!
Currently, there is no implementation for this feature due to limited time from available contributors. However, we understand the value of using emptyDir storage in scenarios like yours, where persistence is not required but fast recovery is essential. While it's not on the roadmap right now, we’re staying focused on the most pressing needs given our resources.
We encourage anyone interested to contribute, and we'd be happy to review any PRs around this functionality.
Thanks again for your input, and please feel free to reach out if you have more ideas!
What is the motivation or use case for the feature?
I don't need persistence for my use case. Restarting the whole keydb cluster can start without any data, but when a cluster node goes down (because of e.g. hardware failure) it should start as soon as possible and get the current data as soon as possible. This works better without persistent volumes.
Describe the solution you'd like
Using
emptyDir
storage instead.The text was updated successfully, but these errors were encountered: