| From: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
|---|---|
| To: | kaido vaikla <kaido(dot)vaikla(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Frequent failover |
| Date: | 2023-11-07 05:44:25 |
| Message-ID: | CAJk5AtYUYN44=0C-XGe1N24f0YrGoDKSM+_eLwQZadbi1a9z3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)vaikla(at)gmail(dot)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
> Kaido
>
> On Mon, 6 Nov 2023 at 04:53, Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)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..
>>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2023-11-07 07:30:15 | Re: TRIGGER on a FOREIGN Table? |
| Previous Message | David G. Johnston | 2023-11-07 04:18:34 | Re: TRIGGER on a FOREIGN Table? |