Configure servers

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

Step 1: Prepare operating systems

Operating systems for OAT and OCP

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

Operating systems for OceanBase Database

You can install OceanBase Database on the Linux operating systems listed in the following table.

Step 2: Configure BIOS for OceanBase Database

Special settings

• In the Intel x86 architecture, we recommend that you:

  • Run the following command to set vm.swappiness to 0 in the /etc/sysctl.conf configuration file:

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

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

    [root@xxx /]
    $sysctl -p    
    

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

• In the ARM and Hygon architecture, we recommend that you run the following command to set the values of the kernel.numa_balancing, vm.zone_reclaim_mode, and vm.swappiness parameters to 0 in the /etc/sysctl.conf configuration file:

  [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

• Cstate

• Pstate

• EIST

• Power saving

BIOS options to be configured

• Automatic Power on After Power Loss: Always on

• Intel Virtualization Technology: Enable in virtualized scenarios and disable in non-virtualized scenarios

• Hyper-threading: Enable

• Hardware prefetcher: Disable

• VT-d: Enable in virtualized scenarios and disable in non-virtualized scenarios

• SR-IOV: Enable in virtualized scenarios and disable in non-virtualized scenarios

• SMMU/IOMMU (IOMMU for the AMD architecture and SMMU for the ARM architecture): Enable in virtualized scenarios and disable in non-virtualized scenarios

• Turbo Mode: Disable

• Energy performance: Enable the maximum performance

  Note

  The methods for modifying the BIOS settings vary among different servers. For specific operation steps, see the operation instructions of your server.

Step 3: Mount disks

• The following table lists the disk mounting point requirements for an OCP server.

  Mounting point	Size	Description	Disk format
  /home	100 GB to 300 GB	The operation log disk of the components.	Ext4 or XFS is recommended.
  /data/log1	3 to 4 times the memory size	The log disk of the OCP MetaDB.	Ext4 or XFS is recommended.
  /data/1	Depends on the size of data to be stored	The data disk of the OCP MetaDB.	Ext4 or XFS is recommended.
  /docker	200 GB to 500 GB	The docker root directory.	Ext4 or XFS is recommended.

• The following table lists the disk mounting point requirements for an OBServer node.

  Mounting point	Size	Description	File system format
  /home	100 GB to 300 GB	The operation log disk of the observer process.	Ext4 or XFS is recommended.
  /data/log1	3 to 4 times the memory size	The log disk of the observer process.	Ext4 or XFS is recommended.
  /data/1	Depends on the size of data to be stored	The data disk of the observer process.	Ext4 or XFS is recommended.

  Note

  We recommend that you allocate at least 50 GB for a root directory. If you use Logical Volume Manager (LVM), we recommend that you specify the stripe parameters during the creation of directories. Here is an example:

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

Step 4: Configure your NICs

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

• You can name the bond mode as bond0 and choose mode1 or mode4. mode4 is recommended. If you use mode4, you must configure 802.3ad for the switch.
• We recommend that you name the NICs as eth0 and eth1.

Recommendations for the I/O scheduler of SSDs

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

Notes

OceanBase Database 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 have added requirements for the instruction sets that run in the X86 architecture. Before the OBServer process starts, the system checks whether the current environment supports the AVX instruction set. If the AVX instruction set is missing, the OBServer process is prohibited from starting.