posts/postgresql-high-availability/ #334
Replies: 4 comments 5 replies
-
Great walk through. Typo on the VIP "ping 192.168.60.100" instead of "192.168.60.110". Also i am working to figure out how to have the network being handled by Tailscale. Stuck at the VIP part but gaining some progress. |
Beta Was this translation helpful? Give feedback.
-
In the Verifying Our Postgres Cluster section, the ports are wrong, you have :8080 but should be 8008 :) But thanks for this guide.. |
Beta Was this translation helpful? Give feedback.
-
Hey, thanks for the Guide. I am stuck at the Patroni Part, seems Patroni is not able to connect to etcd. I get a 404 not found Error on Patroni Logs. Etcd itself is working fine. Patroni Logs: Feb 24 00:00:05 pg3node1.example.com patroni[2328]: 2025-02-24 00:00:05,446 ERROR: Failed to get list of machines from https://192.168.25.102:2380/v3: <Unknown error: '404 page not found', code: 2> Etcd: sudo etcdctl \
|
Beta Was this translation helpful? Give feedback.
-
This tutorial is great, but it is missing one critical thing to be production ready.... It doesn't have backups configured |
Beta Was this translation helpful? Give feedback.
-
posts/postgresql-high-availability/
Today is the day that you start running PostgresSQL in a cluster! In this tutorial we’ll be setting up a production ready Postgres cluster that’s highly available and fault tolerant using PostgreSQL, etcd, Patroni, HA Proxy, and keepalived. This resilient combination will ensure that you can always reach your database even when a node in the cluster goes down!
https://technotim.live/posts/postgresql-high-availability/
Beta Was this translation helpful? Give feedback.
All reactions