Installing Greenplum Workload Manager
- Red Hat Enterprise Linux (RHEL) 64-bit 5.5+ or 6 or CentOS 64-bit 5.5+ or 6
- Greenplum Database version 4.3.x
- Pivotal Greenplum Command Center installer
Note: The Greenplum Workload Manager installer is included in the Pivotal Greenplum Command Center installer you download from Pivotal Network. The installer file,
gp-wlm.bin, is in the Greenplum Command Center installation directory,
/usr/local/greenplum-cc-web, by default.
Running the Greenplum Workload Manager Installer
Greenplum Workload Manager is installed on the Greenplum Database master node. It automatically distributes the software to all segment servers in the database cluster. The installer detects the installed Workload Manager version, if any, and performs an upgrade if necessary. Run the
./gp-wlm.bin package installer with the
--force option to force reinstallation of the current version or an earlier version.
The package installer has the following syntax:
./gp-wlm.bin --help ./gp-wlm.bin --install=<DIR> [ --force ] [ --install-concurrency=<COUNT> ] [ --no-remove-old ] [ --skip-health-check ] [ --dbname-records=<database_name> ] [ --tool-manifest=<FILE> ]
Displays command syntax for the
--install option is required. It specifies the directory where Greenplum Workload Manager will be installed, for example
The installer checks the currently installed version and only performs an upgrade if the current version is older than the installer version. The
--force option skips the version check and performs the upgrade.
The maximum number of hosts to bootstrap at once. The default count is computed by the installer. This option places a limit on the number of processes the installer can fork.
By default, the installer removes all previous installation directories after an upgrade. The
--no-remove-old option prevents the installer from removing old installation directories.
Do not perform a cluster health check after Workload Manager installation completes. This option is not recommended.
The name of the database where the
gp_wlm_records table is created. The default is postgres. The
template1 databases may not be specified. The database must exist at install time. The same database must be specified when upgrading to a new Workload Manager release.
--tool-manifest option specifies a text file containing a list of commands and their absolute paths. Workload Manager normally finds standard system commands on the path. If your environment has incompatible implementations of these commands on the path, create a manifest file that provides the absolute path to a standard version.
Following is an example tools manifest file:
stat=/home/gpadmin/bin/stat readlink=/bin/readlink ssh=/home/me/bin/myssh
The installer creates a
gp-wlm-data directory in the installation directory and installs the Greenplum Workload Manager release into it. A symbolic link
gp-wlm in the installation directory links to the specific Greenplum Workload Manager release directory.
- Log in to the Greenplum master host as the
Ensure that the Greenplum Workload Manager installer is executable.
$ chmod +x gp-wlm.bin
Run the Greenplum Workload Manager installer. Specify the absolute path to an installation directory where you have write permission. For example:
$ ./gp-wlm.bin --install=/home/gpadmin/
This command installs Greenplum Workload Manager in the
gp-wlm-datasubdirectory on all of the segments and creates the
gp-wlmsymbolic link. For example, the above command installs Workload Manager in
/home/gpadmin/gp-wlm-data/gp-wlm-releaseand creates the symbolic link
Note: In rare cases, the installer can fail during the
cluster-health-checkphase. If the cluster is reported not healthy, re-run the installer with the
For convenience you may source
<INSTALL_DIR>/gp-wlm/gp-wlm_path.shto add the Workload Manager executables to your path.
To uninstall Greenplum Workload Manager, run the following command:
$ <INSTALL_DIR>/gp-wlm/bin/uninstall --symlink <INSTALL_DIR>/gp-wlm