Shuts down and then restarts a HAWQ system after shutdown is complete.
hawq restart <object> [-l|--logdir <logfile_directory>] [-q|--quiet] [-v|--verbose] [-M|--mode smart | fast | immediate] [-u|--reload] [-m|--masteronly] [-R|--restrict] [-t|--timeout <timeout_seconds>] [-U | --special-mode maintenance] [--ignore-bad-hosts cluster | allsegments]
hawq restart -? | -h | --help hawq restart --version
hawq restart utility is used to shut down and restart the HAWQ server processes. It is essentially equivalent to performing a
hawq stop -M smart operation followed by
The <object> in the command specifies what entity should be started: e.g. a cluster, a segment, the master node, standby node, or all segments in the cluster.
hawq restart command runs, the utility uploads changes made to the master
pg_hba.conf file or to the runtime configuration parameters in the master
hawq-site.xml file without interruption of service. Note that any active sessions will not pick up the changes until they reconnect to the database.
postgresdatabase listener process, for example), it may take longer to start up due to the database recovery and validation process. If not specified, the default timeout is 600 seconds.
Fast shut down interrupts and rolls back any transactions currently in progress .
Immediate shutdown aborts transactions in progress and kills all
postgres processes without allowing the database server to complete transaction processing or clean up any temporary or in-process work files. Because of this, immediate shutdown is not recommended. In some instances, it can cause database corruption that requires manual recovery.
gp_maintenance_connparameter is set.
Restart a HAWQ cluster:
$ hawq restart cluster
Restart a HAWQ system in restricted mode (only allow superuser connections):
$ hawq restart cluster -R
Start the HAWQ master instance only and connect in utility mode:
$ hawq start master -m PGOPTIONS='-c gp_session_role=utility' psql