pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Frequent failover
Date: Tue, 7 Nov 2023 08:59:19 -0600
Message-ID: <678bb3fe-eead-454e-8c8c-5e0fb49100af@gmail.com> (raw)
In-Reply-To: <CAJk5AtaHK2w8w5aQ1AOB7S5cfnAxWZMNrqvcCWKc1RhRXEJ7EA@mail.gmail.com>
References: <CAJk5AtbOUbFikUN8My-NPnV3CZ0J14dhaNbZRfb4FaqsCarUiQ@mail.gmail.com>
	<CA+427g9qkZB4ptN6SS6OhkkeHh1HzK6Ojx9Y5rfpffP-wFFzCQ@mail.gmail.com>
	<CAJk5AtYUYN44=0C-XGe1N24f0YrGoDKSM+_eLwQZadbi1a9z3Q@mail.gmail.com>
	<9cabf7bc-e98f-449c-82ce-446727ff4814@gmail.com>
	<CAJk5AtaHK2w8w5aQ1AOB7S5cfnAxWZMNrqvcCWKc1RhRXEJ7EA@mail.gmail.com>

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.

view thread (6+ messages)

Message-ID: <678bb3fe-eead-454e-8c8c-5e0fb49100af@gmail.com>
Permalink:  ../678bb3fe-eead-454e-8c8c-5e0fb49100af@gmail.com/
Also on:    postgresql.org/message-id/678bb3fe-eead-454e-8c8c-5e0fb49100af@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Frequent failover
  In-Reply-To: <678bb3fe-eead-454e-8c8c-5e0fb49100af@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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