gpstart
Starts a Apache Cloudberry system.
Synopsis
gpstart [-d <coordinator_data_directory>] [-B <parallel_processes>] [-R]
[-m] [-y] [-a] [-t <timeout_seconds>] [-l <logfile_directory>]
[--skip-heap-checksum-validation]
[-v | -q]
gpstart -? | -h | --help
gpstart --version
Description
The gpstart
utility is used to start the Apache Cloudberry server processes. When you start a Apache Cloudberry system, you are actually starting several postgres
database server listener processes at once (the coordinator and all of the segment instances). The gpstart
utility handles the startup of the individual instances. Each instance is started in parallel.
As part of the startup process, the utility checks the consistency of heap checksum setting among the Apache Cloudberry coordinator and segment instances, either enabled or deactivated on all instances. If the heap checksum setting is different among the instances, an error is returned and Apache Cloudberry does not start. The validation can be deactivated by specifying the option --skip-heap-checksum-validation
.
Note Before you can start a Apache Cloudberry system, you must have initialized the system using
gpinitsystem
. Enabling or deactivating heap checksums is set when you initialize the system and cannot be changed after initialization.
If the Apache Cloudberry system is configured with a standby coordinator, and gpstart
does not detect it during startup, gpstart
displays a warning and lets you cancel the startup operation.
-
If the
-a
option (deactivate interactive mode prompts) is not specified,gpstart
displays and logs these messages:Standby host is unreachable, cannot determine whether the standby is currently acting as the coordinator. Received error: <error>
Continue only if you are certain that the standby is not acting as the coordinator.It also displays this prompt to continue startup:
Continue with startup Yy|Nn (default=N):
-
If the
-a
option is specified, the utility does not start the system. The messages are only logged, andgpstart
adds this log message:Non interactive mode detected. Not starting the cluster. Start the cluster in interactive mode.
If the standby coordinator is not accessible, you can start the system and troubleshoot standby coordinator issues while the system is available.