Hello,
Thank you for your reply
Patroni replied this:
"It seems your system is under so much stress that there was no resources
for Patroni to execute HA loop for 35 seconds.
This interval exceeds ttl=30s, therefore the leader key expired, Patroni
noticed it and demoted Postgres.
You need to fi
Yi Sun writes:
> Besides command run(like pg_ctl) can cause "received immediate shutdown
> request" any other reason can cause this please?
That message indicates that something sent the postmaster process a
SIGQUIT signal (which is all that "pg_ctl stop -m immediate" does).
There's no speculati
Hi guys,
Besides command run(like pg_ctl) can cause "received immediate shutdown
request" any other reason can cause this please?
This production DB, support colleague said didn't run it
Yi Sun 于2020年11月18日周三 上午11:54写道：
> Hi all
>
> There are 3 nodes in our prd db in patroni cluster, vm01 is
Hi all
There are 3 nodes in our prd db in patroni cluster, vm01 is leader, vm02
and vm03 are standby, vm01 received immediate shutdown request caused
failover to vm02, after that vm03 received fast shutdown request
As vm03 not in cluster so have to reinit vm03
What's the possible root caused vm
