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

This topic contains release notes for Greenplum Command Center 6.7.

Supported Platforms

Greenplum Command Center 6.7 is compatible with the following platforms.

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

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

Release 6.7.1

Release Date: 2022-05-18

VMware Tanzu Greenplum Command Center 6.7.1 is a maintenance release that resolves several issues and introduces a new feature.

New and Changed Features

Command Center introduces a new server configuration parameter -- gpcc.enable_send_lock_info -- that helps reduce memory consumption; when disabled, Command Center stops collecting lock information for queries. For more information, see the Server Configuration Parameters topic.

Resolved Issues

  • [182068678] Resolved an issue where users creating GPSS jobs could not upload .yaml files using Safari and Firefox.

  • [32131] Resolved an issue where Command Center was continuing to collect lock information when gpcc.enable_send_instrument was disabled, which could cause memory usage to bloat. To resolve this, users can set the new gpcc.enable_send_lock_info server configuration parameter to off.

Release 6.7.0

Release Date: 2022-4-29

VMware Tanzu Greenplum Command Center 6.7.0 is a minor release that includes feature changes and resolves several issues.

New and Changed Features

  • Command Center is now supported on Red Hat Enterprise Linux 8.x.

  • A user can now create Workload Management rules based on CPU skew. For more information, see the Workload Management documentation page.

  • The realtime Query Details page now displays information about the queries being executed inside a function that a running query has called. For more information, see the Query Details documentation page.

  • The realtime Query Details page now displays a query's Process ID. For more information, see the Query Details documentation page.

  • The Query History details page now displays a query's peak memory. For more information, see the Query History Details documentation page.

  • A user can now search query history by query ID, using the Advanced Search tool in the History dashboard. For more information, see the History documentation page.

  • A user can now create and manage from within Command Center GPSS client jobs for loading data from Amazon S3 into Greenplum Database. For more information, see the Data Loading documentation page.

  • The Recommendations page now:

    • includes an "Age Rank" report, which contains recommendations and information related to performing VACUUM FREEZE and VACUUM FULL on tables

    • offers recommendations on which tables should have VACUUM FREEZE performed on them to reduce their age

    • highlights which tables have had VACUUM FREEZE or VACUUM FULL performed on them

    • allows users to export "Age Rank" from the Recommendations report page to identify which tables should have VACUUM FREEZE performed on them

    For more information, see the Recommendations documentation page.

  • The gpmetrics configuration file (gpcc.conf) contains new sections and properties governing various aspects of Command Center behavior:

    • A user can now specify the age a table must reach to prompt Command Center to issue a VACUUM FREEZE recommendation. This is configured with the new age_ratio parameter in the gpcc.conf configuration file.

    • In a new section called pprof a user can configure various properties that govern how Command Center gathers performance data captured in the $GPCC_HOME/logs/*.prof files.

    • In a new section called gpss, a user can configure various properties that govern how Command Center connects with Greenplum Streaming Server (GPSS) in order to load data.

    For more information, see the gpmetrics Configuration File Reference.

  • You can now turn off table statistics collection by setting the stats_check_interval configuration property to -1. For more information, see the gpmetrics Configuration File Reference.

  • Command Center now captures -- in $GPCC_HOME/logs/*.prof files -- backend performance data for use when troubleshooting heap- or CPU-related performance issues with VMware Support. For more information, see Administering Log Files, Work Files, and Performance Data.

  • The gpmetrics schema has a number of changes:

    • The gpmetrics.gpcc_table_info and gpmetrics.gpcc_table_info_history tables now contain two new columns: age_percent column, which tracks information for calculating when a table should have VACUUM FREEZE run on it and last_vacuum_freeze, which records the last time that one of VACUUM FULL, VACUUM FREEZE and VACUUM FULL FREEZE was performed on the table. In addition, the last_vacuum_full column has been updated to record the last time VACUUM FULL FREEZE was performed on the table.

    • The gpmetrics schema contains three new user-defined functions: gpcc_queries_top_10_memory_per_resgroup and gpcc_queries_top_10_cpu_per_resgroup -- for retrieving by resource group the top ten queries utilitizing the most memory and CPU, respectively and gpcc_recommendations -- which returns a list of tables in need of a vacuum-related action such as VACUUM, VACUUM FULL, ANALYZE, and VACUUM FREEZE.

    • The gpmetrics.gpcc_wlm_rule table has two new columns: cpuskew_percent and cpuskew_duration_sec. If the CPU skew percent of a query is equal to or higher than cpuskew_percent during cpuskew_duration_sec seconds, Command Center executes this rule.

    • The gpmetrics schema includes two new tables -- gpmetrics.gpcc_gpss_job -- which stores information about data loading jobs -- and gpmetrics.gpcc_gpss_log -- which contains logging-related information for data loading jobs. Both are related to the new data loading feature, which allows users to create and manage Greenplum Database Streaming Server jobs directly from Command Center.

    For more information, see the gpmetrics Schema Reference.

  • There are three new server configuration parameters:

    • gpcc.enable_save_full_query_text - When turned on, Command Center saves the full query text for queries whose text is longer than 100KB

    • gpcc.enable_send_inner_query - When turned on, users can see the statements within functions that the query is calling when they click the Inner Queries tab in the query monitor's Query Detail view.

    • gpcc.enable_send_instrument - When turned off, Command Center does not display some query details -- such as the visual query plan tree -- and some statistics. This reduces Command Center's memory consumption.

    For more information, see the Server Configuration Parameters.

Resolved Issues

[32032] Resolved a memory issue caused by long query texts.

[32083] Resolved a crash issue caused by inner queries.

Known Issues

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

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

  • [181943431] Users cannot use the cursor to edit the S3 file location they've entered when creating a data loading job.

  • [32049] Command Center does not monitor FETCH queries.

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

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

check-circle-line exclamation-circle-line close-line
Scroll to top icon