Why gpstate output shows warning "pg_stat_replication shows no standby connections" in Greenplum 6.x
Article ID: 296620
Updated On:
Products
VMware Tanzu Greenplum
Issue/Introduction
In Greenplum 6.x, you might encounter the following warning message when executing "gpstate -e":
Why is this message displayed and does it have any impact on the database?
20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[WARNING]:-pg_stat_replication shows no standby connections
Why is this message displayed and does it have any impact on the database?
Environment
Product Version: 6.11
Resolution
The warning message does not make any impact and should only appear when there are segments down.
The cause of it should be that for a single pair of primary and mirror segments, the mirror segment is playing a standby role to its primary. When a segment is down, causing the interconnection failure between the primary and mirror, the following warning message is displayed: "pg_stat_replication shows no standby connections".
Observe that the number of the warning messages is equal to the number of downed segments:
To get rid of these warning messages, you need to recover the failed segments.
Note: This warning message only appears in Greenplum 6.x so far.
The cause of it should be that for a single pair of primary and mirror segments, the mirror segment is playing a standby role to its primary. When a segment is down, causing the interconnection failure between the primary and mirror, the following warning message is displayed: "pg_stat_replication shows no standby connections".
Observe that the number of the warning messages is equal to the number of downed segments:
[gpadmin@sdw1][~]$ gpstate -e 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:-Starting gpstate with args: -e 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 6.12.1 build commit:7ec4678f29dd922d7d44501f5fc344b5d0d4d49f' 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 9.4.24 (Greenplum Database 6.12.1 build commit:7ec4678f29dd922d7d44501f5fc344b5d0d4d49f) on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 6.4.0, 64-bit compiled on Nov 19 2020 18:59:42' 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:-Obtaining Segment details from master... 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:-Gathering data from segments... 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[WARNING]:-pg_stat_replication shows no standby connections 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[WARNING]:-pg_stat_replication shows no standby connections 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:----------------------------------------------------- 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:-Segment Mirroring Status Report 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:----------------------------------------------------- 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:-Downed Segments (may include segments where status could not be retrieved) 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:- Segment Port Config status Status 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:- sdw3 35556 Up Process error -- database process may be down 20210112:17:44:48:015070 gpstate:sdw1:gpadmin-[INFO]:- sdw3 35557 Up Process error -- database process may be down
To get rid of these warning messages, you need to recover the failed segments.
Note: This warning message only appears in Greenplum 6.x so far.
Feedback
Yes
No
Powered by
