primary processes are started with option "-c gp_role=utility"

Products

• VMware Tanzu Greenplum

Issue/Introduction

After a successful gprecoverseg the recovered segment(s) are started with the option "-c gp_role=utility"

sdw1> ps -aef | egrep -- -D
   :
   :
gpadmin  26929     1  0 10:32 ?        00:00:00 /usr/local/greenplum-db-6.23.4/bin/postgres -D /data/primary/gp_6.23.3_202311021044_jam_seg0 -p 30274 -c gp_role=utility
   :
   :

When "gprecoverseg" is run to recover a downed segment, it will be started as a mirror with the option "-c gp_rle=utility".
When "gprecoverseg -r" is run to rebalance the cluster, both the primary and mirror will be started with the option.

Environment

Product Version: 6.23

Resolution

The only known impact is with Greenplum Command Center (GPCC). With the option "-gp_role=utility", GPCC metrics collector will not be started.

Workaround:
Restart the database with "gpstop -af" and "gpstart -a" 

Fix:
This ia a known issue in 6.24.x and below.
Upgrade to Greenplum 6.25.0 or above to get the fix.
See "Cluster Management" section in 6.25 Release Notes