Stops or restarts a Greenplum Database system.
gpstop [-d <coordinator_data_directory>] [-B parallel_processes>] [-M smart | fast | immediate] [-t <timeout_seconds>] [-r] [-y] [-a] [-l <logfile_directory>] [-v | -q] gpstop -m [-d <coordinator_data_directory>] [-y] [-l <logfile_directory>] [-v | -q] gpstop -u [-d <coordinator_data_directory>] [-l <logfile_directory>] [-v | -q] gpstop --host <host_namea> [-d <coordinator_data_directory>] [-l <logfile_directory>] [-t <timeout_seconds>] [-a] [-v | -q] gpstop --version gpstop -? | -h | --help
gpstop utility is used to stop the database servers that comprise a Greenplum Database system. When you stop a Greenplum Database system, you are actually stopping several
postgres database server processes at once (the coordinator and all of the segment instances). The
gpstop utility handles the shutdown of the individual instances. Each instance is shutdown in parallel.
The default shutdown mode (
-M smart) waits for current client connections to finish before completing the shutdown. If any connections remain open after the timeout period, or if you interrupt with CTRL-C,
gpstop lists the open connections and prompts whether to continue waiting for connections to finish, or to perform a fast or immediate shutdown. The default timeout period is 120 seconds and can be changed with the
-t timeout\_seconds option.
-M fast shutdown mode to roll back all in-progress transactions and terminate any connections before shutting down.
-u option, the utility uploads changes made to the coordinator
pg_hba.conf file or to runtime configuration parameters in the coordinator
postgresql.conf file without interruption of service. Note that any active sessions will not pick up the changes until they reconnect to the database.
$COORDINATOR_DATA_DIRECTORYwill be used.
The segment instances are not shut down and the utility returns an error in these cases:
This option cannot be specified with the
gprecoversegutility restores segment instances. Run
gprecoversegcommands to start the segments as mirrors and then to return the segments to their preferred role (primary segments).
This mode kills all
postgres processes without allowing the database server to complete transaction processing or clean up any temporary or in-process work files.
gpstopwaits for active user connections to disconnect and then proceeds with the shutdown. If any user connections remain open after the timeout period (or if you interrupt by pressing CTRL-C)
gpstoplists the open user connections and prompts whether to continue waiting for connections to finish, or to perform a fast or immediate shutdown.
gpstopdisplays a message indicating that one or more segments are still in the process of shutting down and that you cannot restart Greenplum Database until the segment instance(s) are stopped. This option is useful in situations where
gpstopis run and there are very large transactions that need to rollback. These large transactions can take over a minute to rollback and surpass the default timeout period of 120 seconds.
pg_hba.conffiles of the coordinator and segments and the runtime parameters of the
postgresql.conffiles but does not shutdown the Greenplum Database array. Use this option to make new configuration settings active after editing
pg_hba.conf. Note that this only applies to configuration parameters that are designated as runtime parameters.
Stop a Greenplum Database system in smart mode:
Stop a Greenplum Database system in fast mode:
gpstop -M fast
Stop all segment instances and then restart the system:
Stop a coordinator instance that was started in maintenance mode:
pg_hba.conf files after making configuration changes but do not shutdown the Greenplum Database array: