This document contains release information about Tanzu Greenplum Command Center 6.8 releases. Greenplum Command Center 6.8 provides management and monitoring functionality for Tanzu Greenplum Database 6.
This topic contains release notes for Greenplum Command Center 6.8.
Greenplum Command Center 6.8 is compatible with the following platforms.
See Tanzu Greenplum Command Center Supported Platforms for the most current compatibility information.
Release Date: 2023-01-13
VMware Tanzu Greenplum Command Center 6.8.4 is a maintenance release that includes one new feature and resolves several issues.
The gpmetrics configuration file --
gpcc.conf -- now includes a set of configuration parameters to customize and optimize the Command Center agents' query sampling behavior. For more information, see the gpmetrics Configuration File Reference.
Release Date: 2022-12-8
VMware Tanzu Greenplum Command Center 6.8.3 is a maintenance release that resolves these issues:
update-extension.txtfile installed with Command Center 6.8.2.
Release Date: 2022-10-03
Release Date: 2022-10-03
VMware Tanzu Greenplum Command Center 6.8.2 is a maintenance release that resolves these issues:
AgentManager: GPCC Version mismatch, Agent <agent>, webserver <webserver>, will be stopped
Release Date: 2022-08-05
VMware Tanzu Greenplum Command Center 6.8.0 is a minor release that includes new and changed features and resolves several issues.
The default location of the
gpmetrics directory is now
$HOME -- the home directory of the user who starts up Command Center -- rather than
If you are upgrading from Command Center 6.7.x or earlier and a directory called
gpmetrics does not already exist under
$HOME, Command Center will migrate the
gpcc-alert.yaml files from
$MASTER_DATA_DIRECTORY/gpmetrics directory to
If a directory called
gpmetrics does already exist under
$HOME, you must copy the
gpcc-alert.yaml files over manually before starting Command Center 6.8.0 for the first time.
To specify a default location different than
$HOME for the
gpmetrics directory, configure the
gpmetrics_home parameter in the
app.conf file. For more information, see the Command Center Console Parameters topic.
For more information, see Install the Greenplum Command Center Software.
A user can now configure Command Center to purge history data that exceeds the specified retention period. For more information, see the History Settings topic.
A user can now create Workload Management rules for logging queries that match a particular condition. For more information, see the Workload Management documentation page.
A user can now filter queries by by department name, using the Advanced Search tool in the Query Monitor dashboard. For more information, see the Query Monitor documentation page.
A user can now search query history by department name, using the Advanced Search tool in the History dashboard. For more information, see the History documentation page.
A user can now see the timestamp of each inner query.
A user can now view the size of a table on the table detail page in the Table Browser.
The realtime Query Details page now displays a list of the tables the query has accessed. For more information, see the Query Details documentation page.
The Query History details page now displays a list of the tables the query has accessed. For more information, see the Query History Details documentation page.
gpmetrics schema has the following changes:
gpmetrics.gpcc_queries_history table now has a column called
access_tables_info, which stores the table OIDs of the tables the query accessed.
gpmetrics.gpcc_table_info_history tables now have a column called
last_size_ts, which stores the time when the current table's size column was last updated.
For more information, see the gpmetrics Schema Reference.
This Command Center release introduces a new gpmetrics configuration parameter --
disable_size_check. When set to
true, the Command Center table browser will not collect table size information, in order to prevent performance issues when there are a large number of tables. For more information, see the gpmetrics Configuration File Reference.
This Command Center release introduces a new console parameter --
XSRFSecure -- to protect the cookie Command Center uses. For more information, see the Command Center Console Parameters topic.
 Resolved an issue where using "@" or "/" in the user field of the Command Center authentication screen resulted in an error.
 Resolved an issue where users could not use the cursor to edit the S3 file location they entered when creating a data loading job.
The following are known issues in the current Greenplum Command Center release.
 If a user creates a data loading job with the same data source and target table as an existing job, the existing job will be updated even if it was created by a different user.
 Command Center does not monitor FETCH queries.
 Submitting a large query string with
psql -c or libraries causes Command Center performance issues.
 When the "Query is blocked for xxx minutes" alert is triggered, the query ID shown on the notification feed may be incorrect.
[178295227"] Resource group assignment by a query tags rule has no effect if the query tags are defined by
PGOPTIONS with single quotes.
 When Daylight Saving Time occurs, Command Center requires a restart to repopulate certain data metrics.
 When using the
gppersistentrebuild utility, the Last Accessed column in the Table Browser view might be refreshed, although no queries accessed the tables.
 When you define a workload management rule that uses the Planner Cost condition, the input field transforms your entry to a double datatype value. This can limit the ability to accurately define large planner costs that may be necessary for the GPORCA optimizer. For example, if you enter the GPORCA maximum cost value as 1457494496834852608, the actual value is converted to 1457494496834852600 for the rule. The value shown in the completed rule definition is the value that the rule enforces, and it may not be the exact value that you entered. Increase the cost value as necessary to cover the cost you want to set as the maximum.
 If you recreate the
gp_wlm extension from outside of Command Center after you have already created workload management rules using the Command Center interface, the rules engine may not run for a period of roughly 1 hour. This behavior occurs because Command Center checks for the availability of the extension every hour. Any changes you make outside of Command Center in this situation will not be visible until Command Center checks for the extension, or until you login to Command Center and access the Workload> Workload Mgmt page.
 If you upgrade your Command Center installation using the
gpccinstall -u option and you also specify an SSH binary using the
-ssh-path <path> option, the customized SSH path will not be used during the installation and the
ssh_path parameter will not be set in the
When viewing the Table Browser view, the calculated size for a partitioned table is incorrect if some child partitions are in different schemas than the root table.
If there are a large number of tables in a schema in a database, sorting the partition table list by size can take a long time to display.