Tanzu Greenplum® Command Center 6.5 Release Notes

Updated 2021-May-31

About This Release

This document contains release information about Tanzu Greenplum Command Center 6.5. Greenplum Command Center 6.5 provides management and monitoring functionality for Tanzu Greenplum Database 6.

This topic contains release notes for Greenplum Command Center 6.5.

Supported Platforms

Greenplum Command Center 6.5 is compatible with the following platforms.

  • Tanzu Greenplum Database 6.x.
  • Red Hat Enterprise Linux 6.x1 and 7.x
  • CentOS 6.x1 and 7.x
  • SUSE Enterprise Linux 12
  • Ubuntu 18.04

See Tanzu Greenplum Command Center Supported Platforms for the most current compatibility information.

Enhancements and Changes in Greenplum Command Center 6.5

New and Changed Features

  • The Query Monitor page now allows users to filter queries displayed based on the Status of the query: Running, Queued, or Blocked. For more information, see the Query Monitor documentation page.

  • The Query Monitor page now contains an Advanced Search tool. The tool allows users to filter queries displayed based on query metrics such as query ID, database name, resource group, and more. For more information, see the Query Monitor documentation page.

  • A user can now pause the Query Monitor in order to view a snapshot of queries. For more information, see the Query Monitor documentation page.

  • The Query Monitor now displays a variety of information about sessions, such as session status, associated users and databases, idle time, and associated queries. A user with Admin or Operator permission can see and cancel all users’ sessions, as well as export session details to a CSV file. For more information, see the Query Monitor documentation page.

  • The realtime Query details page now displays the query’s query tags.

  • The Query History details page now displays the query’s query tags.

  • On the History page, the Advanced Search tool now allows users to filter on a query’s query tags. For more information, see the History documentation page.

  • A user can create a workload rule to terminate idle sessions and can examine rule logs of terminated sessions. For more information, see the Workload Management documentation page.

  • A user can create rules by spill file size. For more information, see the Workload Management documentation page.

  • The gpmetrics schema contains a new gpmetrics.gpcc_queries_now table that stores real-time query metrics data.
    The gpcc_wlm_rule table has two additional rows: one for storing parameters for idle session kill rules, and one for storing spill file size.
    For more information, see the gpmetrics Schema Reference documentation page.

  • Microsoft IE is no longer a supported browser for Command Center.

Resolved Issues

  • [176183074] - Resolved CORS security issues.

  • [31245] - The gpcc_queries_now table is now available as part of the gpmetrics schema. For more information , see the gpmetrics Schema Reference documentation page.

  • [31229] - Resolved an issue in which queries with long query text were blocking.

  • [31473] - Resolved an issue in which Command Center was sending alert emails too frequently.

  • [31443] - Resolved an issue in which Command Center reported blocked DDL queries as running.

  • Known Issues

The following are known issues in the current Greenplum Command Center release.

Query tags rule not enforced when query tags are surrounded by single quotes

Resource group assignment by a query tags rule has no effect if the query tags are defined by PGOPTIONS with single quotes.

Requirement for a trusted certificate, even when insecure authentication is enabled

When the “Allow insecure authentication” setting is enabled, but the email protocol is STARTTLS, Command Center ignores the setting and still expects a trusted certificate.

Command Center requires restart after Daylight Savings Time

When Daylight Saving Time occurs, Command Center requires a restart to repopulate certain data metrics.

Last Accessed column affected by persistent table rebuild

When using the gppersistentrebuild utility, the Last Accessed column in the Table Browser view might be refreshed, although no queries accessed the tables.

Limitation for Defining Planner Cost in Workload Rules

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.

External Updates to Workload Management Rules are Delayed

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.

Customized SSH Path Not Supported with the Upgrade (-u) Option

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 app.conf file.

Calculated Root Table Size Inaccurate for Some Partitioned Tables

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.

Sorting Tables by Size on Partition List Page is Slow

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.