Greenplum Command Center(GPCC) causing high memory usage when running "Table Size Check"

Products

• VMware Tanzu Data Suite
• VMware Tanzu Data Suite
• Greenplum
• VMware Tanzu Greenplum

Issue/Introduction

The Out Of Memory killer (oom-killer) in the OS can kill the queries that are run by GPCC to capture the table sizes.

Disabling the "Table Size Check” will stop the OOM-killer events from occurring.

Cause

A query that the GPCC used to get the table size consumes a lot of memory on Greenplum 7.x, this happens when table size update is enabled and it will use the User Defined Function(UDF) gpcc_filenode_scan() to get the table size.

The SQL for the function has been rewritten to improve the performance and reduce the memory used.

Resolution

Fix

Fixed in GPCC 7.2.