Crank up the log level in both Postgresql and Patroni.
On 11/7/23 07:31, Rajesh Kumar wrote:
I saw only the follow in postgres logs.
57P01 terminating due to administrative command
57P03 database shutting down
..then "received fast shutdown request",,,,postmaster
Have you scoured the Patroni and Postgresql logs?
Have you increased the logging level?
On 11/6/23 23:44, Rajesh Kumar wrote:
Is there a way to narrow down the cause of failover? Yesterday itself failover happened 7 times.
Hi
First of all, read a logs.
$PGDATA/log
#journalctl -u patroni
I had once failover flapping, because of master heavy load, caused by apliccation change. So, find a pattern.
If physical replication, after failover you don't need run a vacuum manually if autovacuum is enabled.
br
Kaido
Hi,
When I issue command patronictl history, I can see frequent failover. Like atleast weekly once.
Every time this happened we have to do vacuum analyse for all dba.
So, I need assistance in how to avoid frequent failovers and what is the solution for vacuum part we r doing..
--
Born in Arizona, moved to Babylonia.
--
Born in Arizona, moved to Babylonia.