Are you an LLM? You can read better optimized documentation at /en/docs/latest/getting_started/preparing_for_installation.md for this page in Markdown format
This section describes how to prepare and configure an environment for simplified openGauss installation. The simplified installation can be performed on a single node or on primary/standby nodes. Read this section carefully before installation. If the configuration in this section has been completed, skip this section.
Download the installation package of the corresponding platform from the openGauss community.
Log in to the openGauss community and download the latest installation package of the corresponding platform. For individual developers or non-enterprise-level environments, download the simplified installation package (without installing components such as the OM).
Click Download.
Check the installation package.
Decompress the installation package and check whether the installation directory and files are complete. Run the following commands in the directory where the installation package is stored:
Run the ls command to display information similar to the following:
total 90296drwx------ 3 root root 4096 Mar 31 21:18 bindrwx------ 3 root root 4096 Mar 31 21:18 etcdrwx------ 3 root root 4096 Mar 31 21:18 includedrwx------ 4 root root 4096 Mar 31 21:18 jredrwx------ 5 root root 4096 Mar 31 21:18 libdrwx------ 5 root root 4096 Mar 31 21:18 sharedrwx------ 2 root root 4096 Mar 31 21:18 simpleInstall-rw------- 1 root root 32 Mar 31 21:18 version.cfg
You can obtain the installation package from the openGauss open-source community.
Preparing the Software and Hardware Installation Environment
This section describes the preparations for installation. It is recommended that servers to be deployed on openGauss have the same software and hardware configurations.
Table 1 lists the minimum hardware requirements of the openGauss server. When planning the hardware configuration of a product, consider the data scale and expected database response speed. Plan hardware as required.
Table 1 Hardware requirements
Item
Configuration Description
Memory
It is recommended that the memory be 32 GB or above for function debugging. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
In performance tests and commercial deployment, it is recommended that the memory be 128 GB or above for single-instance deployment. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
Complex queries require much more memory, and therefore, the memory may be insufficient in high-concurrency scenarios. In this case, it is recommended that a large-memory server or load management be used to restrict concurrences on the system. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
CPU
It is recommended at least one 8-core 2.0 GHz CPU be used for function debugging. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
In performance tests and commercial deployment, it is recommended that one 16-core 2.0 GHz CPU be used. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
Both
You can set CPUs to hyper-threading or non-hyper-threading mode. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
Note:
For individual developers, the minimum configuration is 2 cores and 4 GB memory, and the recommended configuration is 4 cores and 8 GB memory. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
Currently, openGauss supports only the CPUs of ARM servers and x86_64-based universal PC servers. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
Disk
Hard disks used for installing openGauss must meet the following requirements:
At least 1 GB is used to install the openGauss applications.
About 300 MB is used for each host to store metadata.
More than 70% of available disk space is reserved to store data.
You are advised to configure the system disk to RAID 1 and data disk to RAID 5 and plan four groups of RAID 5 data disks for installing openGauss. RAID configuration is not described in this document. You can configure RAID by following instructions in the hardware vendors' manuals or using common methods found on the Internet. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
openGauss supports using an SSD with the SAS API and NVMe protocol deployed in RAID mode as the primary storage device of the database. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
Network Requirements
Minimum 300 Mbit/s Ethernet is required. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
You are advised to bond two NICs for redundancy. For details about how to configure it, see the instructions in the manual provided by the hardware manufacturer. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
The current installation package can be used only on the English operating system. Set Disk Cache Policy to Disabled to avoid data loss in an unexpected power-off.
Linux file system
It is recommended that the number of remaining inodes be greater than 1.5 billion.
Table 3 describes the openGauss software dependency requirements.
You are advised to use the default installation packages of the dependent software in the listed OS installation CD-ROMs or sources. If the software does not exist, refer to the recommended versions of the software.