This topic describes the hardware requirements for a server, including the operating system, BIOS settings, disk mounting, network card settings, and software requirements.
Prepare the operating system
OceanBase Database can be installed in the Linux operating systems listed in the following table.
Linux operating system |
Version |
Server architecture |
|---|---|---|
| Alibaba Cloud Linux | 2 | x86_64, ARM_64 |
| AnolisOS | 8.6 and later | x86_64 (including Hlgo), ARM_64 (including Kunpeng and Phytium) |
| KylinOS | V10 | x86_64 (including Hlgo), ARM_64 (including Kunpeng and Phytium) |
| Unity Operating System (UOS) | V20 | x86_64 (including Hlgo), ARM_64 (including Kunpeng and Phytium) |
| NFSChina OS | 4.0 and later | x86_64 (including Hlgo), ARM_64 (including Kunpeng and Phytium) |
| Inspur KOS | 5.8 | x86_64 (including Hlgo), ARM_64 (including Kunpeng and Phytium) |
| CentOS / Red Hat Enterprise Linux | 7.x, 8.x | x86_64 (including Hlgo), ARM_64 (including Kunpeng and Phytium) |
| SUSE Enterprise Linux | 12SP3 and later | x86_64 (including Hlgo) |
| Debian | 8.3 and later | x86_64 (including Hlgo) |
| openEuler | 20.03 LTS SP1/SP2 and 22.10 LTS | x86_64 (including Hlgo), ARM_64 (including Kunpeng and Phytium) |
Note
- The operating system must be configured with a network and a software manager (yum or zypper).
- The server where OceanBase cluster is deployed must be in little-endian mode.
BIOS settings
Special settings:
In an Intel x86 environment:
We recommend that you modify the
/etc/sysctl.conffile and set thevm.swappinessparameter to0.[root@xxx /] $vi /etc/sysctl.conf vm.swappiness = 0Apply the values in the sysctl.conf configuration file:
[root@xxx /] $sysctl -pWe recommend that you enable NUMA in an AMD- or ARM-based environment.
We recommend that you modify the configuration file
/etc/sysctl.confin an ARM or Hlgo architecture environment and set the parameterskernel.numa_balancing,vm.zone_reclaim_mode, andvm.swappinessto0.[root@xxx /] $vi /etc/sysctl.conf kernel.numa_balancing = 0 vm.zone_reclaim_mode = 0 vm.swappiness = 0
Apply the values in the sysctl.conf configuration file:
[root@xxx /]
$sysctl -p
BIOS must have the following options disabled:
Cstate
Pstate
EIST
Power saving
SMMU (ARM)
You need to configure the following options in the BIOS:
Automatic Power on After Power Loss: Always on
Intel Virtualization Technology: Enable
Serial port redirection (SOL console redirection): enabled
Hyper-threading: enabled
Hardware prefetcher: Enabled
VT-d: Enable
SR-IOV: Enable
Turbo Mode: Enabled
Energy performance: Maximum performance
Note
BIOS on different servers is modified in different ways. For more information, see the documentation specific to the server.
Disk mounting
The following table describes the disk mounting requirements for OCP servers.
Mount pointSizePurposeDisk format/home 100 GB to 300 GB The log disk for components to store their operation logs. We recommend that you use ext4 or xfs. /data/log1 3 to 4 times the size of the memory The log disk for the OCP metadata database to store its logs. We recommend that you use ext4 or xfs. /data/1 Varies depending on the size of data to be stored The data disk for the OCP metadata database to store its data. We recommend that you use ext4 or xfs. /docker 200 GB to 500 GB The root directory for Docker to store its images and containers. We recommend that you use ext4 or xfs. The following table describes the disk mounting requirements for OBServer servers.
Mount pointSizePurposeFile system format/home 100 GB to 300 GB The log disk for the OBServer node to store its operation logs. We recommend that you use ext4 or xfs. /data/log1 3 to 4 times the size of the memory The log disk for the OBServer node to store its logs. We recommend that you use ext4 or xfs. /data/1 Varies depending on the size of data to be stored The data disk for the OBServer node to store its data. We recommend that you use ext4 or xfs. The following table describes the disk mounting requirements for OMS servers.
Mount pointSizePurposeFile system format/data/oms 400 GB, which can vary depending on the size of the synchronization objects, the number of synchronization jobs, the frequency of DML operations on the synchronization objects, and the retention period of the store component. The data disk for the OMS store component to store its data. We recommend that you use ext4 or xfs. Note
We recommend that you allocate at least 50 GB for the root directory. If you use LVM, we recommend that you create a logical volume with the striping parameter. Here is an example:
lvcreate -n data -L 3000G obvg --stripes=3 --stripesize=128
Network card settings
We recommend that you configure two 10-Gigabit Ethernet network cards.
- Name the bonding interface bond0 or mode1 or mode4. We recommend that you use mode4. If you use mode4, configure 802.3ad on the switch.
- We recommend that you name the network cards eth0 and eth1.
- We recommend that you use the network service and not NetworkManager.
Software requirements
To deploy the OAT GUI, ODC, and OMS, you need to install Docker on these servers. The following table describes the version requirements.
Software |
Version |
|---|---|
| Docker | Docker CE 17.03 and later |
