YMatrix
Quick Start
Simulate Time Series Scenarios
Standard Cluster Deployment
Data Modeling
Connecting to The database
Data Writing
Data Migration
Data Query
Scene Application Examples
Federal Query
Maintenance and Monitoring
Global Maintenance
Partition Maintenance
Backup and Restore
Cluster Expansion
Enable Mirroring
Resource Management
Security
Monitoring
Performance Tuning
Troubleshooting
Reference Guide
Tool Guide
Data Type
Storage Engine
Execution Engine
Stream Processing
DR (Disaster Recovery)
Configuration Parameters
Index
Extension
SQL Reference
FAQ
The gpstart tool is used to start the MatrixDB cluster server process. When the user starts a MatrixDB cluster, the user actually starts multiple postgres database server listener processes (Master and all Segment instances) at the same time. The gpstart tool handles the startup of each instance. Each instance is started in parallel.
Parameter name | Description |
---|---|
-a | Do not prompt the user to confirm |
-B parallel_processes | Number of Segments started in parallel. If not specified, the tool will start up to 64 parallel processes, depending on how many Segment instances need to be started. |
-d master_data_directory | Master host's data directory. The value set by $MASTER_DATA_DIRECTORY is used by default. |
-l logfile_directory | Directory to write to the log file. The default is ~/gpAdminLogs. |
-m | Only start the Master instance, this may be useful for maintenance tasks. After using this option to start, only Master is allowed to be connected in utility mode. For example: ` PGOPTIONS='-c gp_role=utility' psql |
-q | Operate in silent mode. The command output is not displayed on the screen, but is still written to the log file. |
-R | Start the MatrixDB database in restricted mode (only allow database superuser connections). |
-t timeout_seconds | Specifies the timeout (seconds) waiting for the Segment instance to start. If a Segment instance is shut down abnormally (for example due to a power failure or terminated its postgres database listener process), it may take a long time to start due to the database recovery and verification process. If not specified, the default timeout is 60 seconds. |
--skip-heap-checksum-validation | Specify this option at startup, and the heap table checksum consistency between the Master and Segment is not checked. Starting the MatrixDB cluster without performing this verification will cause data loss. This option can only be used if the heap table checksum verification error must be ignored to recover data or to perform error debugging. |
-v | Shows detailed status, progress and error messages output by the tool. |
-y | Do not start the Standby instance. The default is to start the Standby instance and synchronization process. |
-? or -h or --help | Show help information. |
--version | Show version information. |
Start MatrixDB cluster (no prompt for confirmation):
gpstart -a