Greenplum Command Center stops streaming metrics in its dashboard if Coordinator Port is changed

Products

• VMware Tanzu Data Suite
• VMware Tanzu Greenplum
• VMware Tanzu Greenplum / Gemfire

Issue/Introduction

After changing the Coordinator Port in 'postgresql.conf > port' from its default of of '5432', GPCC's dashboard graphs show a spinning indicator without showing data. GPCC logs display:

failed to acquire resources on one or more segments

Environment

Greenplum 6.X

Greenplum 7.X

Greenplum Command Center 7.2.9

Cause

Even though Postgres successfully starts on the new non-default port, GPCC is still pulling metrics using the value stored for dbid 1 in the gp_segment_configuration table.

Resolution

Log in to psql cli on the Coordinator and update the port value for the Coordinator (dbid 1), where 'NEW PORT' is the new non-default value for the Coordinator as reflected in postgres.conf:

update gp_segment_configuration set port = 5432 where port = NEW PORT;

Restart GPCC

Additional Information

Your browser may be holding on to cached information and not immediately display streamed data in the dashboard. To verify the fix, open an incognito browser to GPCC