#RNDate#2022-05-24
OceanBase Cloud Platform (OCP) has been upgraded to support more features and has been optimized for SQL diagnostics. In this version, the following features are provided: decoupling of primary and standby databases, and more.
V3.3.1
Version information
Version: V3.3.1
Previous version: V3.3.0
Version release date: May 24, 2022
Supported upgrade path: You can directly upgrade OCP V2.3.x and later to this version. To upgrade OCP versions earlier than V2.3.0, you must first upgrade them to V2.3.x and then to this version.
Supported OceanBase Database versions
OCP V3.3.1 supports the following OceanBase Database versions:
OceanBase V1.4.x
OceanBase V2.1.x
OceanBase V2.2.x
OceanBase V3.1.x
OceanBase V3.2.x
New features
VPC support
The ECS type is added to the host type. You can select the ECS type for hosts in the host list, when you import a host, or when you create or scale out an OceanBase cluster or an OBProxy cluster.
The network attribute is displayed on the frontend page in scenarios such as host, OceanBase cluster, and OBProxy cluster.
You can filter hosts by network type in the maintenance of an OceanBase cluster or an OBProxy cluster.
Multi-condition alert feature
You can configure multiple alert expressions for multiple monitoring metrics in the CLI. The AND and OR operators are supported.
Multiple monitoring metrics can be displayed in the alert details page.
When you modify the alert expressions for multiple monitoring metrics in the GUI, a prompt "Cannot edit" is displayed.
The OAS alert items are built in to facilitate seamless integration with OAS.
OAS data query capability
The monitoring query feature is enhanced to better support OAS. The following multi-condition expressions are supported, and the ROUND function is also supported.
= (equivalent to:)
!=
=~ (regular expression match)
!~ (non-regular expression match)
The kern.log log collection is added to the log trace feature.
Several monitoring data items, such as io_await and partition_iutil, are added to meet OAS requirements.
Multilingual documentation
The documentation is available in both Simplified Chinese and English, and is adapted to different language environments to ensure a consistent user experience.
Fixed issues
OCP V3.3.1 fixes the following issues:
The FullGC issue under high pressure (20000 QPS).
The error that occurs when the sampling strategy is deleted during backup and restore.
The error that occurs when the agent upgrade step fails during the upgrade of OCP V3.2.3 to a later version on an ARM architecture.
The error that occurs when you upgrade ob2230 to ob3230 by using OCP V3.3.0.
The issue where a read-only cluster can modify the tenant replicas.
The false alert issue of the NTP service in a container environment.
The issue where the Primary Zone information of a tenant is not synchronized.
The issue where a tenant cannot be created on ob1479 by using OCP.
The issue where the Python alert script template is outdated.
The issue where the sys tenant has a long-term SlowSQL alert.
The issue where the alert redirection logic is incorrect.
The issue where the sum of the response ratios in SQL diagnostics is not 100%.
Other issues in SQL diagnostics, monitoring, and alerts under specific conditions.
Some frontend page interaction issues.
Known issues
No. |
Known issue |
Workaround |
|---|---|---|
| 1 | The tenant creation task fails when the nls_comp parameter is set to ANSI. | This issue does not affect the business. We recommend that you do not use this parameter when you create a tenant. |
| 2 | The agent is reinstalled successfully during the OCP upgrade, but the upgrade still fails. | This issue does not affect the business. You can ignore it. |
| 3 | After you stop the observer process in the topology view, no option is provided to restart the process. | This issue does not affect the business. You can ignore it. |
Version limitations
- Hardware requirements
OCP-Server can be installed on a physical server or in a Docker container. OCP-Server supports multi-node high availability deployment.
The following table lists the minimum hardware requirements for OCP-Server nodes.
Hardware |
Requirement |
|---|---|
| CPU | |
| Memory | 16 GB of available memory |
| NIC | 10 Gbps NIC |
OCP-Agent consumes very few resources and has no special requirements on the hardware resources of the installation node.
- Operating system requirements
The following table lists the operating system requirements for installing OCP Server (including OCP-Agent).
Server type |
Operating system |
Supported versions |
|---|---|---|
| x86_64 | RHEL | 7.2 and later |
| x86_64 | CentOS | 7.2 and later |
| x86_64 | AliOS | 7.2 and later |
| x86_64 | openSUSE | 12 SP3 and later |
| ARM aarch64 | AliOS | 7.2 and later |
| ARM aarch64 | NeoKylin | 7.6 |
| ARM aarch64 | Huawei EulerOS | 2.0 SP8 |
- Client requirements
General users usually access OCP services through a Web browser. The following table lists the client requirements.
Browser |
Minimum version |
|---|---|
| Chrome | 81 |
| Firefox | 64 |
| Safari | 10 |
| Edge | 13 |
If you want to access OCP services from an iOS device, the following table lists the operating system requirements.
Operating system |
Minimum version |
|---|---|
| iOS | 10 |
We recommend that you use a display with a resolution greater than 1440 x 810 for the best user experience.
V3.3.1 BP
Version information
Version: V3.3.1 BP
Previous version: V3.3.1
Version release date: July 8, 2022
Supported upgrade path: You can directly upgrade OCP V2.3.x and later to this version. To upgrade OCP versions earlier than V2.3.0, you must first upgrade them to V2.3.x and then to this version.
New features
Session management displays client port information.
The AWR report displays I/O statistics.
Fixed issues
OCP V3.3.1 BP fixes the following issues:
The issue where the SSH latency is displayed as undefinedms in the host time of the cluster health inspection.
The issue where a false alert is generated when the CPU system usage rate of a server is too high.
The issue where a large number of SQL IDs are generated on the SQL diagnostics page, causing slow queries.
The issue where the ocp-obcloud-service module is missing in the OCP V3.3.1 pom file.
The issue where the initialization of OBConnector times out because of a single-threaded initialization.
