20240305:17:04:47 gpdr:gpadmin:cdw:3242568-[DEBUG]:-Running command: gpdr promote 20240305:17:04:47 gpdr:gpadmin:cdw:3242568-[INFO]:-Promoting recovery cluster 20240305:17:04:47 gpdr:gpadmin:cdw:3242568-[DEBUG]:-setting recovery_target_action to promote on all segments 20240305:17:04:48 gpdr:gpadmin:cdw:3242568-[DEBUG]:-update postgresql.conf ports on all segments 20240305:17:04:49 gpdr:gpadmin:cdw:3242568-[DEBUG]:-setting archive_mode to off on all segments 20240305:17:04:50 gpdr:gpadmin:cdw:3242568-[DEBUG]:-setting archive_command to '' on all segments 20240305:17:04:52 gpdr:gpadmin:cdw:3242568-[DEBUG]:-setting synchronous_standby_names to '' on all segments 20240305:17:04:53 gpdr:gpadmin:cdw:3242568-[DEBUG]:-Start cluster 20240305:17:04:54 gpdr:gpadmin:cdw:3242568-[INFO]:-Waiting for all segments to start up 20240305:17:05:06 gpdr:gpadmin:cdw:3242568-[INFO]:-All segments are ready 20240305:17:05:06 gpdr:gpadmin:cdw:3242568-[DEBUG]:-Updating gp_segment_configuration table 20240305:17:05:06 gpdr:gpadmin:cdw:3242568-[DEBUG]:-Deleting mirror entries from table 20240305:17:05:06 gpdr:gpadmin:cdw:3242568-[DEBUG]:-Stop cluster using pg_ctl in no-wait modeIt will hang at the line "[INFO]:-All segments are ready" if not using the verbose output or at the line "[DEBUG]:-Stop cluster using pg_ctl in no-wait mode" if verbose option is being used.
gpcc stopIf the above does not resolve the issue, check if there are any connections to the DB:
ps -aef | egrep con[0-9]
If there are connections that cannot be easily killed, shutdown the master DB with:
pg_ctl -D ${MASTER_DATA_DIRECTORY} -m fast