Re: Frequent failover
| От | Rajesh Kumar |
|---|---|
| Тема | Re: Frequent failover |
| Дата | |
| Msg-id | CAJk5AtYUYN44=0C-XGe1N24f0YrGoDKSM+_eLwQZadbi1a9z3Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Frequent failover (kaido vaikla <kaido.vaikla@gmail.com>) |
| Ответы |
Re: Frequent failover
|
| Список | pgsql-admin |
Is there a way to narrow down the cause of failover? Yesterday itself failover happened 7 times.
On Mon, 6 Nov, 2023, 1:34 PM kaido vaikla, <kaido.vaikla@gmail.com> wrote:
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
KaidoOn Mon, 6 Nov 2023 at 04:53, Rajesh Kumar <rajeshkumar.dba09@gmail.com> wrote: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..
В списке pgsql-admin по дате отправления: