Closed wxmeng04 closed 3 hours ago
I am pretty confident that Patroni successfully works with etcd 3.5. The errors you get are not related to endpoint names. If etcd doesn't like the endpoint it explicitly saying about it and sets the respective HTTP code (e.g. 404). In your case errors are totally different, Patroni simply can't connect to etcd:
I would advise you to check that etcd hosts are accepting TCP connections on the port 2379.
What happened?
When
patroni /etc/patroni/config.yml
was run, the command line has below prompt:I checked the latest documentation of etcd version 3.5 via below link: https://etcd.io/docs/v3.3/dev-guide/api_grpc_gateway/#notes The latest docs says only [CLIENT-URL]/v3/* will be used.
I'm not sure if I have to use a lower version of etcd. For example 3.4.
How can we reproduce it (as minimally and precisely as possible)?
patroni /etc/patroni/config.yml Just run the command as above with the same version etcd and patroni.
What did you expect to happen?
Expect no error
Patroni/PostgreSQL/DCS version
Patroni configuration file
patronictl show-config
Patroni log files
PostgreSQL log files
Have you tried to use GitHub issue search?
Anything else we need to know?
No response