gpsscli start

gpsscli start

(Re)start a Greenplum Streaming Server job.

Synopsis

gpsscli start job_name
     [--quit-at-eof]
     [{--force-reset-earliest | --force-reset-latest | --force-reset-timestamp tstamp}]
     [--config gpsscliconfig.json]
     [--gpss-host host] [--gpss-port port]
     [--no-check-ca] [-l | --log-dir directory] [--verbose]

gpsscli start {-h | --help}

Description

The gpsscli start command (re)starts a job submitted to a specific Greenplum Streaming Server (GPSS) instance. You identify the name of the job. You can also identify the data offset from which you want the operation to begin.

When you start a job, you initiate the data load operation. The job transitions from the Stopped to the Running state.

If the GPSS instance to which you want to send the request is not running on the default host (127.0.0.1) or the default port number (5000), you can specify the GPSS host and/or port via command line options.

Options

job_name
The identifier of a previously-submitted GPSS job. You can specify a job name when you run gpsscli submit, or the command returns a unique job identifier.
--quit-at-eof
When you specify this option, gpsscli start reads all pending data, stops the job, and then exits. The default behaviour of gpsscli start is to start the job and then exit.
--force-reset-earliest
gpsscli start returns an error if its recorded offset does not match that of the data source. Re-run gpsscli start and specify the --force‑reset‑earliest option to resume the load operation from the earliest available data offset known to the data source.
--force-reset-latest
gpsscli start returns an error if its recorded offset does not match that of the data source. Re-run gpsscli start and specify the --force‑reset‑latest option to load only new data emitted from the data source.
--force-reset-timestamp tstamp
Specify the --force‑reset‑timestamp option to load source data emitted since the specified time. tstamp must specify epoch time in milliseconds, and is bounded by the earliest message time and the current time.
--config gpsscliconfig.json
The GPSS configuration file. This file includes properties that identify the gpss instance that services the command. When SSL encryption is enabled between the GPSS client and server, you also use this file to identify the file system location of the client SSL certificates. Refer to gpss.json for detailed information about the format of this file and the configuration properties supported.
Note: gpsscli subcommands read the configuration specified in the ListenAddress block of the gpsscliconfig.json file, and ignore the gpfdist configuration specified in the Gpfdist block of the file.
--gpss-host host
The GPSS host. The default host address is 127.0.0.1. If specified, overrides a ListenAddress:Host value provided in gpsscliconfig.json
--gpss-port port
The GPSS port number. The default port number is 5000. If specified, overrides a ListenAddress:Port value provided in gpsscliconfig.json
--no-check-ca
Disable certificate verification when SSL is enabled between the GPSS client and server. By default, GPSS checks the certificate authority (CA) each time that you invoke a gpsscli subcommand.
-l | --log-dir directory
The directory to which GPSS writes client command log files. GPSS must have write permission to the directory. GPSS creates the log directory if it does not exist.
If you do not provide this option, GPSS writes gpsscli client log files to the $HOME/gpAdminLogs directory.
--verbose
The default behaviour of the command utility is to display information and error messages to stdout. When you specify the --verbose option, GPSS also outputs debug-level messages about the operation.
-h | --help
Show command utility help, and then exit.

Examples

Start the GPSS job identified by the name nsync_121118:

$ gpsscli start nsync_121118