Tanzu Greenplum® Command Center 6.6 Release Notes

Updated 2021-Nov-15

About This Release

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

This topic contains release notes for Greenplum Command Center 6.6.

Supported Platforms

Greenplum Command Center 6.6 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
  • Ubuntu 18.04

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

Enhancements and Changes in Greenplum Command Center 6.6

New and Changed Features

  • The realtime Query details and Query History details pages now display:

    • the top 5 slices that consume the most CPU time
    • the top 5 slices that consume the most memory
    • the top 5 slices that use disk I/O

    For more information, see the Query Details and Query History Details documentation pages.

  • A user can now exclude “idle in transaction” sessions when adding or editing an idle session killing rule. For more information, see the Workload Management documentation page.

  • The gpmetrics schema includes new and changed tables:

    • gpmetrics.gpcc_resgroup_history, is a new table that stores the history of the resource consumption of each resource group on each segment
    • gpmetrics.gpcc_department, is a new table that stores department information
    • gpcc_role_department, is a new table that stores information about roles within department
    • The gpmetrics.gpcc_queries_history table includes three new columns: slices_metrics, peak_memory and node_sliceid
    • The gpmetrics.gpcc_plannode_history table’s sliceid column has been deprecated.

    For more information, see the gpmetrics Schema Reference documentation page.

  • The gpmetrics schema now includes user-defined functions:

    • gpcc_delete_department deletes a department name from the gpperfmon database.
    • gpcc_queries_per_hour returns a variety of details about query activity per hour.
    • gpcc_queries_per_user returns, for each user, the number of queries whose runtime is longer than the input interval, per hour, in the specified time range.
    • gpcc_queries_per_user_max_and_total_spill_size returns, for each user, the total spill_size and maximum spill_size per query per hour.
    • gpcc_queries_per_user_max_cpu returns, for each user, the query with the maximum segment and master cpu usage per hour, along with details about the query.
    • gpcc_queries_per_user_max_run_time returns, for each user, the longest running query per hour, along with details about the query.
    • gpcc_queries_per_user_max_skew returns, for each user, the query with the maximum amount of processing skew in the system (skew_cpu) per hour, along with details about the query.
    • gpcc_queries_per_user_rows_out returns, for each user, the query with the maximum rows_out per hour, along with details about the query.
    • gpcc_system_per_hour returns a variety of system information.
    • gpcc_update_department renames a department.

    For more information, see the gpmetrics Schema Reference documentation page.

  • A user can now monitor resource group system information, including:

    • CPU utilization of selected resource groups
    • CPU utilization of a specific resource group
    • Memory utilization of selected resource groups
    • Memory utilization of a specific resource group
    • Concurrency status of selected resource groups

    For more information, see the Managing Resource Groups documentation page.

  • Through a new user management interface, a user can now view information about departments and roles, manage and view permissions for roles, export usage information by role, rename a department name using a user-defined function, and delete unwanted departments from the gpperfmon database using a user-defined function. For more information, see the Managing Users documentation page.

  • Administrators now allow guest users to view the Query Monitor without logging in via the Settings view, rather than the now obsolete Permissions view. For more information, see the Settings documentation page.

  • Administrators now manage permissions via the new User Management view rather than the now obsolete Permissions view.

  • A user can now now determine the TLS cipher suites that Command Center accepts. For more information, see the Command Center Console Parameters documentation page.

Resolved Issues

  • [31132] - Command Center was failing to set up an email alert when the SMTP certificate was invalid, rather than issuing a message explaining to users how to proceed without a valid certificate. This has been resolved.

  • [31508] - Resolved an issue where Command Center was failing to save queries to the query history when there were CTAS queries inside a function.

  • [31531] - The Command Center was using a hard coded initial password for the gpmon role if the password was not created before the installer ran. It now uses a random string generated during installation instead.

  • [31781] - Resolved an issue where the accuracy and last_accuracy_ts fields in the gpmetrics.gpcc_table_info_history table were not being correctly populated when the planrows field in the gpmetrics.gpcc_plannode_history table had a very large value.

  • [31782] - Resolved a memory leak in the Command Center session monitor.

  • [31867] - Resolved an issue where the cpu_segment_percent column of the gpmetrics.gpcc_queries_now table was not matching the Host CPU Total.

  • [31890] - Resolved an issue where, when users executed a query with an extremely long query text it could cause the query to fail, due to an invalid memory alloc request.

  • [178957820] - Resolved an issue where the Query Monitor was refreshing a query list after returning from checking query details when paused.

  • [179418127] - Resolved an issue where Command Center was failing to send alert emails to all recipients if there was just one invalid recipient address.

  • [179666482] - Resolved an issue where Command Center was recording an incorrect spill file size in the gpmetrics.gpcc_queries_history table.

Known Issues

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

  • [31723] Submitting a large query string with psql -c or libraries causes Command Center performance issues.

  • [179572065] 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.

  • [31132] 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.

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

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

  • [174667383] 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.

  • [174395009] 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.

  • [167285013] 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.

  • 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.