pxf cluster

Manage the PXF configuration and the PXF Service instance on all Greenplum Database hosts.

Synopsis

pxf cluster <command> [<option>]

where <command> is:

help
init (deprecated)
migrate
prepare
register
reset (deprecated)
restart
start
status
stop
sync

Description

The pxf cluster utility command manages PXF on the master, standby master, and on all Greenplum Database segment hosts. You can use the utility to:

  • Start, stop, and restart the PXF Service instance on the master, standby master, and all segment hosts.
  • Display the status of the PXF Service instance on the master, standby master, and all segment hosts.
  • Synchronize the PXF configuration from the Greenplum Database master host to the standby master and to all segment hosts.
  • Copy the PXF extension control file from the PXF installation on each host to the Greenplum installation on the host after a Greenplum upgrade.
  • Prepare a new $PXF_BASE runtime configuration directory.
  • Migrate PXF 5 $PXF_CONF configuration to $PXF_BASE.

pxf cluster requires a running Greenplum Database cluster. You must run the utility on the Greenplum Database master host.

(If you want to manage the PXF Service instance on a specific segment host, use the pxf utility. See pxf.)

Commands

help
Display the pxf cluster help message and then exit.

init (deprecated)
The command is equivalent to the register command.

migrate
Migrate the configuration in a PXF 5 $PXF_CONF directory to $PXF_BASE on each Greenplum Database host. When you run the command, you must identify the PXF 5 configuration directory via an environment variable named PXF_CONF. PXF migrates the version 5 configuration to $PXF_BASE, copying and merging files and directories as necessary.
You must manually migrate any pxf-log4j.properties customizations to the pxf-log4j2.xml file.

prepare
Prepare a new $PXF_BASE directory on each Greenplum Database host. When you run the command, you must identify the new PXF runtime configuration directory via an environment variable named PXF_BASE. PXF copies runtime configuration file templates and directories to this $PXF_BASE.

register
Copy the PXF extension control file from the PXF installation on each host to the Greenplum installation on the host. This command requires that $GPHOME be set, and is run once after you install PXF 6.x the first time, or run after you upgrade your Greenplum Database installation.

reset (deprecated)
The command is a no-op.

restart
Stop, and then start, the PXF Service instance on the master, standby master, and all segment hosts.

start
Start the PXF Service instance on the master, standby master, and all segment hosts.

status
Display the status of the PXF Service instance on the master, standby master, and all segment hosts.

stop
Stop the PXF Service instance on the master, standby master, and all segment hosts.

sync
Synchronize the PXF configuration ($PXF_BASE) from the master to the standby master and to all Greenplum Database segment hosts. By default, this command updates files on and copies files to the remote. You can instruct PXF to also delete files during the synchronization; see Options.
If you have updated the PXF user configuration or add new JAR or native library dependencies, you must also restart PXF after you synchronize the PXF configuration.

Options

The pxf cluster sync command takes the following option:

–d | ––delete
Delete any files in the PXF user configuration on the standby master and segment hosts that are not also present on the master host.

Examples

Stop the PXF Service instance on the master, standby master, and all segment hosts:

$ pxf cluster stop

Synchronize the PXF configuration to the standby and all segment hosts, deleting files that do not exist on the master host:

$ pxf cluster sync --delete

See Also

pxf