Some segment postmasters were not reloaded

Products

• VMware Tanzu Data Suite
• Greenplum
• VMware Tanzu Greenplum

Issue/Introduction

Is this an expected behavior of gpstop -u ?

[gpadmin@hostname maint]$ gpstop -u
20250212:09:40:46:2055027 gpstop:hostname:gpadmin-[INFO]:-Starting gpstop with args: -u
20250212:09:40:46:2055027 gpstop:hostname:gpadmin-[INFO]:-Gathering information and validating the environment...
20250212:09:40:46:2055027 gpstop:hostname:gpadmin-[INFO]:-Obtaining Greenplum Coordinator catalog information
20250212:09:40:46:2055027 gpstop:hostname:gpadmin-[INFO]:-Obtaining Segment details from coordinator...
20250212:09:40:46:2055027 gpstop:hostname:gpadmin-[INFO]:-Greenplum Version: 'postgres (Greenplum Database) 7.3.3 build commit:ce20fc237ed7520a2476c96ed7d9edddea136932'
20250212:09:40:46:2055027 gpstop:hostname:gpadmin-[INFO]:-Signalling all postmaster processes to reload
...
20250212:09:40:49:2055027 gpstop:hostname:gpadmin-[INFO]:---------------------------------------------
20250212:09:40:49:2055027 gpstop:hostname:gpadmin-[INFO]:-Some segment postmasters were not reloaded
20250212:09:40:49:2055027 gpstop:hostname:gpadmin-[INFO]:---------------------------------------------
20250212:09:40:49:2055027 gpstop:hostname:gpadmin-[INFO]:-   Host                            Datadir                     Port   Status
20250212:09:40:49:2055027 gpstop:hostname:gpadmin-[INFO]:-   hostname.res.prod.global   /data/coordinator/gpseg-1   5432   u
20250212:09:40:49:2055027 gpstop:hostname:gpadmin-[INFO]:---------------------------------------------

Environment

GPDB 7.x 

Cause

This is reported if a segment or standby coordinator is not running at the time the "gpstop -u" is run,

It is expected behaviour.

Resolution

Recover the failed segment with "gprecoverseg" and/or recover the standby coordinator with "gpinitstandby" command and re-try the command.