BUG #17063: repmgrd_upstream_reconnect getting more - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #17063: repmgrd_upstream_reconnect getting more
Date
Msg-id 17063-9ef13d063a0b627a@postgresql.org
Whole thread Raw
Responses Re: BUG #17063: repmgrd_upstream_reconnect getting more  (Mohan Nagandlla <nagandllamohan@gmail.com>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      17063
Logged by:          Mohan nagandlla
Email address:      nagandllamohan@gmail.com
PostgreSQL version: 13.3
Operating system:   Alpine
Description:

I have installed the repmgr for multi HA replication all are going good but
in some times i am getting this logs how can we debug this 
bash-5.1$ repmgr cluster events
 Node ID | Name     | Event                      | OK | Timestamp
| Details
           

---------+----------+----------------------------+----+---------------------+-----------------------------------------------------------------------------------------
 1       | PG-Node1 | repmgrd_upstream_reconnect | t  | 2021-06-18 07:22:28
| reconnected to upstream node after 0 seconds
           
 1       | PG-Node1 | repmgrd_upstream_reconnect | t  | 2021-06-18 06:39:57
| reconnected to upstream node after 0 seconds
           
 1       | PG-Node1 | repmgrd_upstream_reconnect | t  | 2021-06-18 06:28:33
| reconnected to upstream node after 0 seconds
           
 1       | PG-Node1 | repmgrd_upstream_reconnect | t  | 2021-06-18 05:57:32
| reconnected to upstream node after 0 seconds
           
 1       | PG-Node1 | repmgrd_upstream_reconnect | t  | 2021-06-18 05:35:56
| reconnected to upstream node after 0 seconds
           
 1       | PG-Node1 | repmgrd_upstream_reconnect | t  | 2021-06-18 04:36:10
| reconnected to upstream node after 0 seconds
           
 1       | PG-Node1 | repmgrd_upstream_reconnect | t  | 2021-06-18 04:26:18
| reconnected to upstream node after 0 seconds


pgsql-bugs by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
Next
From: PG Bug reporting form
Date:
Subject: BUG #17064: Parallel VACUUM operations cause the error "global/pg_filenode.map contains incorrect checksum"