-
Notifications
You must be signed in to change notification settings - Fork 20
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
Patroni Postgresql instance is down due to k8s api unavailable #669
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-5311.
|
Sounds the same/similar to #616. Patroni needs the k8s API to track the primary. DCS failsafe mode should keep the cluster up until the k8s API is back. |
Thanks @dragomirp . So iiuc, your team will be working on a feature to enable this mode using the charm? We have an application where we cannot tolerate downtime and we are thinking of switching to the machine charm version of this charm to avoid instability (due to k8s). Thank you very much. |
Thank you @taurus-forever @dragomirp You all rock! |
Steps to reproduce
Example deployment: https://pastebin.canonical.com/p/YRyVgZpxC5/
Expected behavior
Cluster does not fail on K8s API unavailability.
Actual behavior
We received the alert
which caused our application to fail because it could only use read-only transactions:
The Patroni logs indicate that the root cause was the unavailability of the k8s api:
It took about 10 minutes to get the cluster back to a healthy state.
Versions
Operating system:
Juju CLI: 3.5.3-ubuntu-amd64
Juju agent: 3.5.3
Charm revision: 239
microk8s:
Log output
Patronoi logs:
Additional context
The text was updated successfully, but these errors were encountered: