kubegres icon indicating copy to clipboard operation
kubegres copied to clipboard

Published 20 hours ago • verified publisher icon reactive-tech

Feature Request - Failover without new Replication

Open Y0ngg4n opened this issue 3 years ago • 3 comments

Would be nice if you could implement Failover without creating new Pods. So if primary fails it selects randomly one of the replication nodes and promotes it as primary until original primary node is back up.

Y0ngg4n avatar Feb 10 '22 12:02 Y0ngg4n

That seems very logical to me - I don’t need another statefulset/pod when I already have a few to spare.

joes avatar Feb 10 '22 18:02 joes

exactly

Y0ngg4n avatar Feb 10 '22 19:02 Y0ngg4n

It seems I was needing the same thing here:

https://github.com/reactive-tech/kubegres/issues/88#issuecomment-1040351243

joes avatar Feb 15 '22 14:02 joes