Обсуждение: Frequent failover

Поиск
Список
Период
Сортировка

Frequent failover

От
Rajesh Kumar
Дата:
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..

Re: Frequent failover

От
kaido vaikla
Дата:
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..

Re: Frequent failover

От
Rajesh Kumar
Дата:
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..

Re: Frequent failover

От
Ron
Дата:
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.

Re: Frequent failover

От
Rajesh Kumar
Дата:
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.

Re: Frequent failover

От
Ron
Дата:
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.