pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedFrequent failover
6+ messages / 3 participants
[nested] [flat]
* Frequent failover
@ 2023-11-06 02:53 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Rajesh Kumar @ 2023-11-06 02:53 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
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..
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Frequent failover
@ 2023-11-06 08:04 kaido vaikla <kaido.vaikla@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: kaido vaikla @ 2023-11-06 08:04 UTC (permalink / raw)
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
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.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..
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Frequent failover
@ 2023-11-07 05:44 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
parent: kaido vaikla <kaido.vaikla@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Rajesh Kumar @ 2023-11-07 05:44 UTC (permalink / raw)
To: kaido vaikla <kaido.vaikla@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
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
> Kaido
>
> On 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..
>>
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Frequent failover
@ 2023-11-07 13:09 Ron <ronljohnsonjr@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Ron @ 2023-11-07 13:09 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
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.
>
> 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
> Kaido
>
> On 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..
>
--
Born in Arizona, moved to Babylonia.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Frequent failover
@ 2023-11-07 13:31 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
parent: Ron <ronljohnsonjr@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Rajesh Kumar @ 2023-11-07 13:31 UTC (permalink / raw)
To: Ron <ronljohnsonjr@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
I saw only the follow in postgres logs.
57P01 terminating due to administrative command
57P03 database shutting down
..then "received fast shutdown request",,,,postmaster
On Tue, 7 Nov 2023, 18:39 Ron, <ronljohnsonjr@gmail.com> wrote:
> 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.
>
> 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
>> Kaido
>>
>> On 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..
>>>
>>
> --
> Born in Arizona, moved to Babylonia.
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Frequent failover
@ 2023-11-07 14:59 Ron <ronljohnsonjr@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 0 replies; 6+ messages in thread
From: Ron @ 2023-11-07 14:59 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
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
>
>
>
> On Tue, 7 Nov 2023, 18:39 Ron, <ronljohnsonjr@gmail.com> wrote:
>
> 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.
>>
>> 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
>> Kaido
>>
>> On 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..
>>
>
> --
> Born in Arizona, moved to Babylonia.
>
--
Born in Arizona, moved to Babylonia.
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2023-11-07 14:59 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-11-06 02:53 Frequent failover Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-11-06 08:04 ` kaido vaikla <kaido.vaikla@gmail.com>
2023-11-07 05:44 ` Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-11-07 13:09 ` Ron <ronljohnsonjr@gmail.com>
2023-11-07 13:31 ` Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-11-07 14:59 ` Ron <ronljohnsonjr@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox