Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-check Primary-Failover / Disabling Fail-Over-Management #177

Open
clauspruefer opened this issue Mar 15, 2024 · 1 comment
Open

Re-check Primary-Failover / Disabling Fail-Over-Management #177

clauspruefer opened this issue Mar 15, 2024 · 1 comment

Comments

@clauspruefer
Copy link

"It manages fail-over: if a Primary PostgreSql crashes, it automatically promotes a Replica PostgreSql as a Primary."

  1. How is this feature tested? Is it rock solid?
  2. Is it possible to disable this feature?

Due to the fact that kubernetes network is virtualized, it should work 100%, in bare-metal scenarios switch / hardware outages can lead to split-brain scenario. This should be re-verified on kubernetes.

@alex-arica
Copy link
Member

alex-arica commented Mar 26, 2024

Yes it is possible to disable it.
More details in the doc here:
https://www.kubegres.io/doc/properties-explained.html#spec_failover

It was rock tested however, as you pointed out Kubernetes network can be unstable on some cloud provider leading to Kubernetes reporting that an instance of Postgres is not healthy. When this happens, Kubegres might trigger a failover.
But the failover itself was rock tested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants