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
Is your feature request related to a problem? Please describe
Currently, the cluster auto-failover feature is not available in Garnet. Do you have any plans to include this feature? If so, could you share the timeline? Additionally, I believe this feature is essential, so I kindly request that you consider this request.
Describe the solution you'd like
Currently, the cluster auto-failover feature is not available in Garnet. Do you have any plans to include this feature? If so, could you share the timeline? Additionally, I believe this feature is essential, so I kindly request that you consider this request.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
+1 for this ask. Looks like primitives for this are already present with AOF, Failover and Replicas support.
While I understand from other issues that something like this may not be on the immediate roadmap, any guidance on how to achieve automatic graceful failover and recovery would be very handy for those of us wanting to design something of our own.
Feature request type
sample request
Is your feature request related to a problem? Please describe
Currently, the cluster auto-failover feature is not available in Garnet. Do you have any plans to include this feature? If so, could you share the timeline? Additionally, I believe this feature is essential, so I kindly request that you consider this request.
Describe the solution you'd like
Currently, the cluster auto-failover feature is not available in Garnet. Do you have any plans to include this feature? If so, could you share the timeline? Additionally, I believe this feature is essential, so I kindly request that you consider this request.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: