Alexander Kukushkin

Well, it is your task to configure it.

I don't have anything to add to my [previous answer](https://github.com/zalando/patroni/issues/2327#issuecomment-1148576860) except maybe asking you to go through Patroni [tutorial](https://github.com/patroni-training/2019).

If something isn't right you'll see it immediately in logs. Also, if watchdog is required, node can't become a leader if watchdog isn't working.

> I was just curious if there is any info available other than log or running lsof command. No, there is nothing. If the _automatic_ mode is chosen you already...

> However, it seems to me, that python-etcd 0.4.5 does not have support for v3, Patroni implements v3 on its own (via JSON gRPC gateways). But, it still relies on...

> but I assumed that if etcdctl can get the members fine, it should work? Not necessarily. etcdctl uses gRPC directly, but Patroni have no other choice as relying on...

> Also, I still get those errors periodically: Every minute: ERROR: watchprefix failed: ProtocolError("Connection broken: InvalidChunkLength(got length b'', 0 bytes read)", InvalidChunkLength(got length b'', 0 bytes read)) In order to...

The value under basebackup has to be the list, you can't do it with `patronictl edit-config -s`

`basebackup` is a default replica creation method.

> Now my etcd cluster has 5 nodes. So I want update patroni configuration Great, unless you set `etcd3.use_proxies` Patroni already knows about new Etcd nodes (there is automatic discovery)....