Greenplum Database Server Configuration Parameters
Greenplum Database gpperfmon Database
gpperfmon_port server configuration parameters must be set in the server configuration file (
postgresql.conf) to enable the Greenplum Database gpperfmon data collection agents. Installing the gpperfmon database with the
gpperfmon_install command and supplying the
--enable command-line option enables the parameters in the configuration file.
To disable the
gpperfmon service, use the
gpconfig command-line utility:
$ gpconfig -c gp_enable_gpperfmon -v off
The Greenplum Database instance must be restarted for the changes to take effect.
The following Greenplum Database server configuration parameters configure the
Turns on the Command Center data collection agent for a segment. Must be set in all
postgresql.conf files (master and all segments).
The default port for the Command Center agents is 8888, but you can set this parameter to a different port if required (master and all segments).
Sets the frequency in seconds that the Greenplum Database server processes send query execution updates to the Command Center agent processes.
This parameter is enabled by default and must remain enabled. It allows the use of external tables that execute OS commands or scripts on the segment hosts. The Command Center agents use this type of external tables to collect current system metrics from the segments.
Controls which message levels are written to the gpperfmon log. Each level includes all the levels that follow it. The later the level, the fewer messages are sent to the log. The default value is warning.
A comma-separated list of shared libraries that are to be preloaded when Greenplum Database starts. The workload management and query metrics extension libraries must be included in this configuration parameter to use Greenplum Command Center.
When on, enables query metrics collection. The default is off. After setting this configuration parameter, Greenplum Database must be restarted for the change to take effect.
The amount of shared memory, in kilobytes, allocated for query metrics. The default is 5120 and the maximum is 131072. At startup, if
gp_enable_query_metrics is set to on, Greenplum Database allocates space in shared memory to save query metrics. This memory is organized as a header and a list of slots. The number of slots needed depends on the number of concurrent queries and the number of execution plan nodes per query. The default value, 5120, is based on a Greenplum Database system that executes a maximum of about 250 concurrent queries with 120 nodes per query. If the
gp_enable_query_metrics configuration parameter is off, or if the slots are exhausted, the metrics are maintained in local memory instead of in shared memory.