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

The following table lists the operating systems that support OceanBase Admin Toolkit (OAT) and OceanBase Cloud Platform (OCP).

Operating systems supported by OceanBase Database

The following table lists the Linux operating systems that support installation of OceanBase Database.

BIOS settings for OceanBase Database servers

Special settings

• In an Intel x86 architecture environment:

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

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

    Apply the values configured in the sysctl.conf configuration file:

    [root@xxx /]
    $sysctl -p    
    

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

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

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

  Apply the values configured in the sysctl.conf configuration file:

  [root@xxx /]
  $sysctl -p
  

BIOS options to be disabled

• C-State

• P-State

• EIST

• Power saving

• SMMU (ARM architecture)

BIOS options to be configured

• Automatic Power on After Power Loss: Always on

• Intel Virtualization Technology: Enable

• Hyper-Threading: Enable

• Hardware prefetcher: Enable

• VT-d: Enable

• SR-IOV: Enable

• Turbo Mode: Enable

• Energy Performance: Maximum Performance

  Note

  The methods for modifying BIOS settings vary among different servers. For specific operations, see the server operation manual.

Disk mounting

• Disk mounting point requirements for OCP servers are shown in the following table.

  Mounting point	Size	Purpose	Disk format
  /home	100 GB~300 GB	Operation log disk for components	Ext4 or XFS is recommended
  /data/log1	3~4 times the memory size	OCP MetaDB log disk	Ext4 or XFS is recommended
  /data/1	Depends on the required storage size for data	OCP MetaDB data disk	Ext4 or XFS is recommended
  /docker	200 GB~500 GB	Docker root directory	Ext4 or XFS is recommended

• Disk mounting point requirements for OBServer nodes are shown in the following table.

  Mounting point	Size	Purpose	File system format
  /home	100 GB~300 GB	Operation log disk of the observer process	Ext4 or XFS is recommended
  /data/log1	3~4 times the memory size	Log disk of the observer process	Ext4 or XFS is recommended
  /data/1	Depends on the required storage size for data	Data disk of the observer process	Ext4 or XFS is recommended

  Note

  We recommend that the root directory is at least 50 GB. If you use LVM, we recommend that you use stripe parameters when creating directories. Example:

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

NIC settings

We recommend that you configure two 10 Gbit/s NICs:

• Name the bond mode bond0. You can choose mode1 or mode4, but mode4 is recommended. For mode4, you must configure the 802.3ad protocol on the switch.
• We recommend that you name the NICs eth0 and eth1.

Recommendations for SSD I/O scheduler

• The default I/O scheduler for NVMe SSDs is none, and no adjustment is required.
• For SATA SSDs, we recommend that you set the I/O scheduler to none.

Considerations

OceanBase Database has added requirements for the instruction set when running in an X86 architecture environment in V4.2.5 BP3, V4.2.5 BP4, V4.2.5 BP5, V4.3.5 BP1, V4.3.5 BP2, V4.3.5 BP3, and V4.4.0. The OBServer process checks whether the current environment supports the AVX instruction set before startup. If the AVX instruction set is not supported, startup is prohibited.