(Optional) Creating the gpperfmon Database
This topic describes how to create the gpperfmon database and enable the gpperfmon data collection agents. Command Center no longer has a dependency on the Greenplum Database gpperfmon service, so completing the tasks in this topic is required only if you need the legacy gpperfmon tables for another purpose.
The Command Center installer now creates the gpperfmon database and the gpmon role if they do not already exist, so it is no longer necessary to use the Greenplum Database
If the gpperfmon database has already been created and the gpperfmon service is running, Pivotal recommends that you disable it to reduce system load. To see if the service is enabled, check the value of the Greenplum Database
gp_enable_gpperfmon system configuration parameter.
$ gpconfig -s gp_enable_gpperfmon
To disable the service, set the parameter to
$ gpconfig -c gp_enable_gpperfmon -v off
You must restart Greenplum Database for the change to take effect.
Note that you can continue to run the gpperfmon service (with a performance cost) if you have a requirement to do so, for example a custom management utility that depends on data in the old history tables.
When the gpperfmon data collection agents are enabled, their processes are started and stopped (using
gpstop) on the Greenplum segment hosts along with the Greenplum Database server processes.
Greenplum Database includes a
gpperfmon_install utility that performs the following tasks:
- Creates the Command Center database (gpperfmon).
- Creates the Command Center superuser role (gpmon).
- Configures Greenplum Database server to accept connections from the gpmon role (edits the
- Sets the Command Center server configuration parameters in the Greenplum Database server
gpperfmon_install utility and the agents are part of the Greenplum Database software. The tasks in this topic can be performed before or after the Command Center software is installed.
Log in to the Greenplum master host as the gpadmin user.
$ su - gpadmin
Source the path file from the Greenplum Database installation directory:
$ source /usr/local/greenplum-db/greenplum_path.sh
gpperfmon_installutility with the
--enableoption. You must supply the connection port of the Greenplum Database master server process, and set the password for the gpmon superuser that will be created. For example:
$ gpperfmon_install --enable --password changeme --port 5432
The password you specify is saved in a
.pgpassfile in the gpadmin user’s home directory. See Changing the gpmon Password for steps to change the gpmon password.
Restart Greenplum Database server. The gpperfmon data collection agents do not start until the database is restarted.
$ gpstop -r
pscommand, verify that the data collection process is running on the Greenplum master. For example:
$ ps -ef | grep gpmmon
Run the following command to verify that the gpmon user can authenticate and that the data collection processes are writing to the Command Center database. If all of the segment data collection agents are running, you should see one row per segment host.
$ psql -U gpmon gpperfmon -c 'SELECT * FROM system_now;'
The data collection agents are now running, and your Greenplum system now has a gpperfmon database installed. You can connect to it as follows:
$ psql gpperfmon
gpperfmon_install utility adds entries for the gpmon role to the
pg_hba.conf file, which allows the gpmon role to make a local connection to any database in the Greenplum cluster on the master host.
local gpperfmon gpmon md5 host all gpmon 127.0.0.1/28 md5 host all gpmon ::1/128 md5
These entries provide the gpmon role sufficient access to maintain query history in the gpperfmon database. For Greenplum Command Center, the gpmon user must also have host access from the host where the Command Center web server and backend run. This requires that you add an entry for the Command Center host.
# vi $MASTER_DATA_DIRECTORY/pg_hba.conf
Add the following line to allow the gpmon role to access the gpperfmon database from all hosts in the Greenplum Database cluster. Substitute the IP address of the master host for <cc-host-ip>.
host all gpmon <cc-host-ip>/32 md5
See Changing the gpmon Password for steps to change the gpmon user’s password.
- Copy the
$MASTER_DATA_DIRECTORY/pg_hba.conffile from your primary master host to the same directory on your standby master host. This ensures that the required connection options are also set on the standby master.
- Copy the
.pgpassfile from the gpadmin user’s home directory on your primary master host to the same directory on your standby master host. Set the permissions on the
.pgpassfile to 600 (for example:
chmod 0600 ~/.pgpass).