Environmental Requirements
This document provides guidance based on the Kunpeng server and openEuler OS. Before performing operations, ensure that your software and hardware meet the requirements.
Hardware Requirements
Table 1 lists the hardware requirements.
Item |
Description |
|---|---|
Server |
Kunpeng server |
CPU |
Kunpeng 920 processor |
Drive |
A performance test requires at least one system drive and one data drive. Use an SSD or NVMe drive as the data drive for higher performance. If no performance test is needed, you can create a data directory directly on the system drive. Configure the number of drives based on actual requirements. |
OS Requirements
- Run the cat /etc/*-release command to check the OS information.
Run the lscpu command to check the processor information.
Run the uname -r command to check the kernel version.
Run the uname -a command to check the environment information.
- If you need to install an OS, choose Minimal Install and select Development Tools to minimize manual operations.
Table 2 lists the OS and software requirements.
Network Planning (Multi-Node Installation)
This document plans two nodes in the multi-node installation scenario, including one master node and one segment node (data node). In addition, the master node can also be used as a data node.
Due to the specification limitation on hardware resources, during the use of KAEzip, a large number of processes may preempt hardware resources at the same time in the scenario where a large amount of data, multiple segments, and high concurrency exist. As a result, the hardware bottleneck occurs and the performance deteriorates. According to the test result, in the test environment with a single node, TPC-H 1 TB data volume, and 5 concurrent requests, it is recommended that the number of segments in the initialized database be less than 40.

Table 3 describes the details of the Greenplum cluster network planning.
Node Name |
Node Role |
Network IP Address Example |
Network IP Address Mapping Name |
|---|---|---|---|
master |
Master node |
192.168.2.1 |
gp-mdw |
segment |
Data node |
192.168.2.2 |
gp-sdw NOTE:
For easy identification during the deployment, if multiple data nodes are planned, you are advised to name them gp-sdw1, gp-sdw2, ..., and gp-sdwN. |