What system requirements are there for installing OceanBase Server?
The following table describes the minimum configuration requirements for the servers.
| Server type | Number | Minimum functional configuration | Minimum performance configuration |
|---|---|---|---|
| OCP server | 1 | 16 CPU cores, 32 GB of memory, 1.5 TB of storage | 32 CPU cores, 128 GB of memory, 1.5 TB of SSD storage, and a 10-Gbps network card |
| OceanBase Database Compute Server | 3 | 4 CPU cores, 16 GB of memory,
NoteThe log disk requires more than three times the memory size, and the data disk requires sufficient storage for the target data volume. |
32 CPU cores, 256 GB of memory,
NoteThe log disk requires more than three times the memory size, and the data disk requires sufficient storage for the target data volume. |
If you want the OCP server to provide high availability, you need three OCP servers and a load balancing software or hardware solution such as F5, Alibaba Cloud SLB, or OceanBase Database's ob_dns. In this case, deploy the OCP server in a three-node configuration.
You can install OceanBase Database on 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 HaiGao), ARM_64 (including KungPeng and Phytium) |
| KylinOS | V10 | x86_64 (including HaiGao), ARM_64 (including KungPeng and Phytium) |
| Unity Operating System (UOS) | V20 | x86_64 (including HaiGao), ARM_64 (including KungPeng and Phytium) |
| NFSChina | 4.0 and later | x86_64 (including HaiGao), ARM_64 (including KungPeng and Phytium) |
| Inspur KOS | 5.8 | x86_64 (including HaiGao), ARM_64 (including KungPeng and Phytium) |
| CentOS / Red Hat Enterprise Linux | 7.x, 8.x | x86_64 (including HaiGao), ARM_64 (including KungPeng and Phytium) |
| SUSE Enterprise Linux | 12SP3 and later | x86_64 (including HaiGao) |
| Debian | 8.3 and later | x86_64 (including HaiGao) |
| openEuler | 20.03 LTS SP1/SP2 | x86_64 (including HaiGao), ARM_64 (including KungPeng and Phytium) |
| Nengsi LinxOS | V6.0.99, V6.0.100 | x86_64 (including HaiGao), ARM_64 (including KungPeng and Phytium) |
Note
The operating system must be configured with a network connection and a software management tool (yum or zypper).
How will OceanBase Database be deployed in a production environment?
The following deployment solutions are available:
| Solution | Characteristics | Infrastructure requirements | Scenarios |
|---|---|---|---|
| Single IDC with three replicas | RPO=0, RTO low, automatic switchover in case of failure. It protects against individual hardware failures but not IDC-level or regional disasters. | Single IDC. | Scenarios where IDC-level or regional disaster recovery is not required. |
| Three IDCs in the same region with three replicas | RPO=0, RTO low, automatic switchover in case of failure. It protects against individual hardware failures and IDC-level disasters but not regional disasters. | Three IDCs in the same region. The network latency between IDCs in the same region is low. | Scenarios where IDC-level disaster recovery is required but regional disaster recovery is not. |
| Five IDCs across three regions with five replicas | RPO=0, RTO low, automatic switchover in case of failure. It protects against individual hardware failures, IDC-level disasters, and regional disasters. | Five IDCs across three regions. Two of the regions are relatively close to each other with low network latency. | Scenarios where IDC-level and regional disaster recovery are both required. |
| Two IDCs in the same region with data replication between clusters | RPO>0, RTO high, manual switchover. It protects against individual hardware failures and IDC-level disasters but not regional disasters. | Two IDCs in the same region. | This solution is suitable for scenarios with two IDCs in the same region and disaster recovery requirements at both IDC and regional levels. |
| Three IDCs across two regions with five replicas and data replication between clusters | IDC-level failures: RPO=0, RTO low, automatic switchover. Regional failures: RPO>0, RTO high, manual switchover. It protects against individual hardware failures, IDC-level disasters, and regional disasters. | Three IDCs across two regions. | This solution is suitable for scenarios with three IDCs across two regions and disaster recovery requirements at both IDC and regional levels. |
What is LSE?
LSE is a feature introduced in ARMv8.1, namely, "Large System Extensions" (LSE). LSE provides a set of atomic operations for supporting synchronized and mutually exclusive access in multiprocessor environments. These atomic operations include Load-Exclusive (LDE), Store-Exclusive (STE), and Conditional Compare Exchange (CCXE) instructions. LSE also provides new instructions and memory barriers for maintaining data consistency and sequentiality.
LSE instructions allow efficient access to shared memory and enable finer-grained locking mechanisms and lower overheads. Compared with traditional synchronization instructions, LSE instructions can reduce lock competition, improve concurrent performance, and provide better scalability.
From which OCP version is the nolse package supported?
OCP supports the OceanBase RPM package marked with nolse since V4.3.0. This update addresses the issue of identifying Large System Extensions (LSE) expansion instructions in an ARM CPU.
Considerations for OBD deployment
You can upload both the nolse and no-nolse OceanBase RPM packages at the same time. OBD will adaptively deploy the packages based on the system support. Alternatively, you can upload and install the supported packages as needed.
Considerations for OCP deployment
Although you can upload both the nolse and no-nolse packages to OCP at the same time, OCP does not support adaptive installation. When you deploy a cluster, you need to select whether to install the packages supporting LSE.
