Greenplum Command Center (GPCC) is not showing more than one filespace in the Storage Status page

Products

• VMware Tanzu Greenplum

Issue/Introduction

Symptoms:
When you create another filespace in Greenplum Command Center (GPCC) 4.6.0 and lower, the filespace is not showing up correctly in the GPCC Storage Status page or only one of the filespaces is showing. By design, GPCC is supposed to show all file systems that are used by Greenplum Database (GPDB).

Let's assume the following:

gpperfmon=# select * from pg_filespace;
  fsname   | fsowner 
-----------+---------
 pg_system |      10

gpperfmon=# select * from pg_filespace_entry;
 fsefsoid | fsedbid |              fselocation               
----------+---------+----------------------------------------
     3052 |       1 | /data1/master/gpseg-1
     3052 |       2 | /data1/primary/gpseg0
     3052 |       4 | /data1/primary/gpseg2
     3052 |       3 | /data1/primary/gpseg1
     3052 |       5 | /data1/primary/gpseg3
     3052 |       6 | /data1/mirror/gpseg0
     3052 |       7 | /data1/mirror/gpseg1
     3052 |       8 | /data1/mirror/gpseg2
     3052 |       9 | /data1/mirror/gpseg3

Add a filespace:

gpfilespace --config /var/vcap/store/gpadmin/fs.out

This will add a filespace named "fs_test".
 

gpperfmon=# select * from pg_filespace;
  fsname   | fsowner 
-----------+---------
 pg_system |      10
 fs_test   |      10
(2 rows)

gpperfmon=# select * from pg_filespace_entry;
 fsefsoid | fsedbid |              fselocation               
----------+---------+----------------------------------------
     3052 |       1 | /data1/master/gpseg-1
     3052 |       2 | /data1/primary/gpseg0
     3052 |       4 | /data1/primary/gpseg2
     3052 |       3 | /data1/primary/gpseg1
     3052 |       5 | /data1/primary/gpseg3
     3052 |       6 | /data1/mirror/gpseg0
     3052 |       7 | /data1/mirror/gpseg1
     3052 |       8 | /data1/mirror/gpseg2
     3052 |       9 | /data1/mirror/gpseg3
    17538 |       1 | /var/vcap/store/gpadmin/master/gpseg-1
    17538 |       2 | /var/vcap/store/gpadmin/primary/gpseg0
    17538 |       3 | /var/vcap/store/gpadmin/primary/gpseg1
    17538 |       4 | /var/vcap/store/gpadmin/primary/gpseg2
    17538 |       5 | /var/vcap/store/gpadmin/primary/gpseg3
    17538 |       6 | /var/vcap/store/gpadmin/mirror/gpseg0
    17538 |       7 | /var/vcap/store/gpadmin/mirror/gpseg1
    17538 |       8 | /var/vcap/store/gpadmin/mirror/gpseg2
    17538 |       9 | /var/vcap/store/gpadmin/mirror/gpseg3
(18 rows)

If you go to the GPCC Storage Status page, you would expect to see both /data1 and /var/vcap/store as entries. However, in this case, the only filespace visible is /var/vcap/store:

Environment

Resolution

This issue is resolved in GPCC 4.6.1, which requires you to be on GPDB 5.17.0 or above.