Configure servers

This topic describes the hardware and software configuration requirements for servers, including the operating system, BIOS settings, disk mounting, and NIC settings.

Prepare the operating system

Operating systems for OAT and OCP

OceanBase Admin Toolkit (OAT) and OceanBase Cloud Platform (OCP) can be deployed on the operating systems listed in the following table.

Operating systems for OceanBase Database

OceanBase Database can be installed on the Linux operating systems listed in the following table.

BIOS settings for OceanBase Database server

Special settings

• In an Intel x86 architecture environment:

  • We recommend that you modify the /etc/sysctl.conf file and set the vm.swappiness parameter to 0. The steps are as follows:

    [root@xxx /]
    $vi /etc/sysctl.conf
    vm.swappiness = 0
    

    Apply the values in the sysctl.conf file:

    [root@xxx /]
    $sysctl -p    
    

• In an AMD or ARM architecture environment, we recommend that you enable Numa.

• In an ARM and Hygon architecture, we recommend that you modify the /etc/sysctl.conf configuration file and set the parameters kernel.numa_balancing, vm.zone_reclaim_mode, and vm.swappiness to 0. The steps are as follows:

  [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 file:

  [root@xxx /]
  $sysctl -p
  

BIOS settings to be disabled

• Cstate

• Pstate

• EIST

• Power saving

• SMMU (ARM architecture)

BIOS settings to be configured

• Automatic Power on After Power Loss: Always on

• Intel Virtualization Technology: Enabled

• Hyper-threading: Enabled

• Hardware prefetcher: Enabled

• VT-d: Enabled

• SR-IOV: Enabled

• Turbo Mode: Enabled

• Energy performance: Maximum performance

  Note

  BIOS settings vary by server model. For specific instructions, refer to the server's operation manual.

Mount disks

• The following table describes the disk mount points of an OCP server.

  Mount point	Size	Purpose	Disk format
  /home	100 GB~300 GB	Log disk for running components	Ext4 or XFS is recommended.
  /data/log1	3~4 times the memory size	Log disk for the OCP MetaDB	Ext4 or XFS is recommended.
  /data/1	Depends on the amount of data to be stored	Data disk for the OCP MetaDB	Ext4 or XFS is recommended.
  /docker	200 GB~500 GB	Root directory of Docker	Ext4 or XFS is recommended.

• The following table describes the disk mount points of an OBServer node.

  Mount point	Size	Purpose	File system format
  /home	100 GB~300 GB	Log disk for observer processes	Ext4 or XFS is recommended.
  /data/log1	3~4 times the memory size	Log disk for observer processes	Ext4 or XFS is recommended.
  /data/1	Depends on the amount of data to be stored	Data disk for observer processes	Ext4 or XFS is recommended.

  Note

  We recommend that the root directory be at least 50 GB in size. If you use LVM, we recommend that you specify the striping parameters when you create it. Here is an example:

  lvcreate -n data -L 3000G obvg --stripes=3 --stripesize=128

NIC Settings

It is recommended to configure two 10-Gbit/s NICs:

• Name the bond interface bond0. The bonding mode can be set to mode1 or mode4, but mode4 is recommended. For mode4, configure the switch to support the 802.3ad protocol.
• Name the NICs eth0 and eth1.

Considerations

Starting from V4.2.5 BP3, V4.2.5 BP4, V4.2.5 BP5, V4.3.5 BP1, V4.3.5 BP2, and V4.3.5 BP3, OceanBase Database introduced instruction set requirements for running on x86 architecture. Before startup, the OBServer process checks whether the current environment supports the AVX instruction set. If not, the process will not start.