Pivotal Greenplum® Command Center 6.1.0 Release Notes

Updated 2019-12-13

About This Release

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

See Enhancements and Changes in Greenplum Command Center 6.1 for information about new features and changes in this Command Center release.

Supported Platforms

Greenplum Command Center 6.1.0 is compatible with the following platforms.

  • Pivotal 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 Pivotal Greenplum Command Center Supported Platforms for the most current compatibility information.

Enhancements and Changes in Greenplum Command Center 6.1

Command Center Installation Changes

  • The Command Center release download file names have changed to include the Greenplum Database major version, for example greenplum-cc-web-6.1.0-gp6-rhel7-x86_64.zip.

  • The Command Center installer checks that the metrics collector extension running in the Greenplumn Database system is the correct version for the Command Center version you are installing. If a new metrics collector extension is needed, the installer instructs you to install the correct version using the gppkg utility.

  • The Command Center installer creates four entries in the pg_hba.conf authentication file for the gpmon role if there are no existing gpmon entries.

    local      gpperfmon     gpmon                 md5
    host       all           gpmon   md5
    host       all           gpmon  ::1/128        md5
    host       all           gpmon  samenet        md5

    The samenet entry is new in this release, and the installer will add it to the pg_hba.conf file even when there are existing entries for the gpmon role.

    Note that the Table Browser feature requires all in the database field of the host entries so that gpmon can retrieve table information from each database.

    If you use an authentication method other than md5 for the gpmon user, such as LDAP or Kerberos, edit the pg_hba.conf file to enable connections from all hosts and access to all databases.

New and Changed Features

  • A new Table Browser is added to allow administrators to see information about tables in Greenplum Databases. Tables displayed can be filtered by database, schema, owner, and size. The Command Center interface provides details about tables, including table storage types, distribution policies, partitions, sizes, and last access times. It lists recent queries that have accessed the table, with links into the Command Center query history. Notably, the Table Browser displays only metadata for tables; it does not provide access to data stored in tables.

    Note: When you first start Command Center after installing this version, Command Center loads data into the new gpmetrics.gpcc_table_info table in the gpperfmon database. For databases with large numbers of tables, the initial load could take five minutes or longer. Table data will not be available in the Table Browser until it has been loaded.

  • The table browser uses two new tables in the gpmetrics schema: gpcc_table_info and gpcc_table_info_history. See gpmetrics Schema Reference for information about the contents of these tables.

  • The Command Center web server (gpccws) memory consumption is much improved compared to earlier Command Center versions.

  • On the History page, the count of running queries at any point on the Queries graph now includes queries that started and finished in the interval since the previous metrics sample. A new queries_finished column is added to the gpmetrics.gpcc_database_history table to record this count.

  • The metrics collector extension adds a new gpcc.enable_query_profiling server configuration parameter that can be enabled to help with performance troubleshooting. When off, the default, the metrics collector does not collect queries executed by the gpmon user in the gpperfmon database or plan node history for queries that run in less than ten seconds (or min_query_time, if greater than ten seconds). If you enable gpcc.enable_query_profiling in a session the metrics collector collects those queries. This parameter is available when the MetricsCollector-6.1.0 gppkg or above is installed in Greenplum Database 6.x.

  • Each night, Command Center archives files in the $GPCC_HOME/ccdata directory that are more than two weeks old. The files in this directory include saved query text files (q*.txt), plan node files (gpccexec*.txt), and table size and statistics information files (gpcc_size_info.dat and gpcc_stat_info.dat). Archive files have names in the format archive_YYYYMMDD_YYYYMMDD.tar.gz, where the dates are the beginning and end dates of the week included in the archive. The archived files are no longer needed by Command Center but may be useful for troubleshooting; you can remove them manually if you do not want to save them.

Resolved Issues

  • When a Command Center user signs out of Command Center, the Welcome page is displayed, but the message “Checking DB status…” is displayed for several seconds before the login form is presented. This is fixed. If there are no errors the login form is now displayed immediately.

  • The rightmost edge of system metrics graphs could drop to zero if the metrics data for that period was not yet available to display. This is fixed by cutting the time axis on the right edge of metrics graphs to the last period with available data. As a result of this fix, the time period displayed at the right edge of a graph can be slightly earlier than the last sync time displayed at the top of the page.

  • Users with self-only permissions could see other users’ query history. In Command Center 6.1 users with self-only permission have no access to the query history page, so they cannot see their own or others’ query history. Self-only users will be allowed access to their own query history in a future Command Center release.

  • The Command Center Storage Status page did not display tablespaces with locations other than pg_default or pg_global. This is fixed. Expanding a hostname now shows each tablespace location. Hovering over the tablespace location displays a pop-up with a list of the data directories at that location. Data directories may not be displayed until Command Center has refreshed the Storage Status page, which occurs every four hours.

  • The send_alert.sh script in the $MASTER_DATA_DIRECTORY/gpmetrics directory had a bug that caused some values to be incorrectly expanded when substituted into the template. This is fixed by replacing all occurrences of $ARGUMENT with ${ARGUMENT} in the script. You can implement the same fix if you have created a custom send_alert.sh script.

Known Issues

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

Command Center Installer Truncates pg_hba.conf LDAP Entries

When the Command Center gpccinstall installer updates the pg_hba.conf file it truncates LDAP information on entries that use the ldap authentication method. The truncated information must be reinserted manually after the Command Center installation is complete. This issue exists in Command Center versions 4.7 through 4.9, 6.0, and 6.1.

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.