pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: m.kancevicius@gmail.com
Subject: BUG #18862: using pg_autoctl node_2 cannot bring back from maintenance mode
Date: Mon, 24 Mar 2025 15:28:31 +0000
Message-ID: <18862-b641a5dac163d5ca@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      18862
Logged by:          mindaugas kancevicius
Email address:      m.kancevicius@gmail.com
PostgreSQL version: 16.7
Operating system:   RHEL 8.10
Description:        

Hello,
I am using pg_auto_failover postgresql version 16.7, RHEL 8.10:
monitor node
node_1
node_2
When applying config changes in node_1, enabling maintenance in node_2:
 pg_autoctl enable maintenance
When configuration completed in node_1, disabling maintenance:
pg_autoctl enable maintenance
This command worked fine for 5-7 times when did changes and node_2 catchedup
node_1 TLI: LSN.
When applied the last time enable, disable maintenance it somehow frozen and
received an error when tried to comeback from maintenance mode:
  Name |  Node |               Host:Port |         TLI: LSN |   Connection |
     Reported State |      Assigned State
-------+-------+-------------------------+------------------+--------------+---------------------+--------------------
node_1 |     1 | node_1:5432 |   4: 97/6C000110 |   read-write |            
 single |              single
node_2 |     2 | node_2:5432 |   4: 97/6BD90750 |       none ! |        
maintenance |             catchingup

The last known: TLI: LSN was 97/6BD90338
  Name |  Node |               Host:Port |         TLI: LSN |   Connection |
     Reported State |      Assigned State
-------+-------+-------------------------+------------------+--------------+---------------------+--------------------
node_1 |     1 | node_1:5432 |   4: 97/6BD90338 |   read-write |            
primary |             primary
node_2 |     2 | node_2:5432 |   4: 97/6BD90338 |    read-only |          
secondary |           secondary

This happened for me twice in 2 days after several commands when
enabled/disabled maintenance mode.

Is there any known issue why this happens randomly for node_2.
The only wait how i was able to fix it, i had to drop node_2 from monitor
node and reapply setup on node_2.



view thread (2+ messages)  latest in thread

Message-ID: <18862-b641a5dac163d5ca@postgresql.org>
Permalink:  ../18862-b641a5dac163d5ca@postgresql.org/
Also on:    postgresql.org/message-id/18862-b641a5dac163d5ca@postgresql.org

 · 

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-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, m.kancevicius@gmail.com
  Subject: Re: BUG #18862: using pg_autoctl node_2 cannot bring back from maintenance mode
  In-Reply-To: <18862-b641a5dac163d5ca@postgresql.org>

* 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