OceanBase Cloud Platform (OCP) V3.3.3 is released. This version enhances the password box and inspection features and optimizes other features. It also adapts to the OceanBase Database V3.2.3.1 and V3.2.4.
Version information
Version: V3.3.3
Previous version: V3.3.1
Version release date: July 18, 2022
Supported upgrade path: OCP V2.3.x and later can be directly upgraded to this version. For OCP versions earlier than V2.3.0, you must first upgrade to V2.3.x and then to this version.
Supported OceanBase Database versions
OCP V3.3.3 supports the following OceanBase Database versions:
OceanBase Database V1.4.x
OceanBase Database V2.1.x
OceanBase Database V2.2.x
OceanBase Database V3.1.x
OceanBase Database V3.2.x
New features
Password box
You can import, export, and share the passwords of a cluster or tenant that you have taken over.
You can share the connection credentials in the password box with other OCP users.
Monitoring
The Memory Usage metric is added to the tenant performance monitoring page. This metric displays the percentage of memory used by the tenant on the OceanBase Database side.
Security
The Set Password for Account feature is added. You must change the password of the built-in account when you log in to OCP for the first time.
The prompt about plain text passwords is removed from the browser console to improve system security.
Feature enhancements
OBProxy
You can modify and restart an OBProxy cluster to make the parameter changes take effect.
Inspection
The Cluster Health Inspection feature is unified to the Inspection module. The inspection feature is also optimized.
Version adaptation
OCP V3.3.3 is adapted to OceanBase Database V3.2.4. You can import SRS data when you create a MySQL tenant.
OCP V3.3.3 is adapted to OceanBase Database V3.2.3.1. The way to obtain the kernel version number is adapted to the new rule.
Bug fixes
OCP V3.3.3 fixes the following issues:
The performance of several agents is optimized to improve agent stability.
The logic of the thread pool on the server side is optimized to improve the performance of monitoring queries.
The backup and restore data collection process is optimized to improve the stability of OCP in large-scale backup scenarios.
The real-time of SQL diagnostic data is optimized to improve the speed of OAS in obtaining diagnostic data.
The logic of the admin account organization permission verification is optimized to adapt to the private cloud scenario.
The pre-check process of the default directory when a cluster is created is optimized. If an error occurs, the error is exposed in advance to avoid rolling back the entire task.
The issue that the monagent file handle is left behind is fixed.
The issue that an error is reported when a cluster is connected in a special scenario is fixed.
The issue that the backup and restore scheduling times out is fixed.
The issue that the service list cannot be viewed after the backup and restore system is upgraded from a low version (V2.x) to a high version (3.x) is fixed.
The issue that the backup and restore system fails to filter by status is fixed.
The issue that an NPE is reported on the major compaction management page when no data exists is fixed.
The issue that OCP V3.3.0 fails to be deployed by using OAT is fixed.
The issue that some inspection internationalization issues are fixed.
The issue that the data disk usage exceeds 100% in a special scenario is fixed.
The issue that no alert is reported when the CPU sys usage exceeds the threshold in an abnormal scenario is fixed.
Known issues
No. |
Known issue |
Workaround |
|---|---|---|
| 1 | After an upgrade from V3.1.x to V3.3.3, specific QPS historical data cannot be queried in some scenarios. | This issue does not affect the business. You can ignore it. |
| 2 | In some non-standard scenarios, an NPE is reported when a standby cluster is created in multi-cluster mode. | This issue does not affect the business. You can ignore it. |
| 3 | Some interfaces are continuously requested twice when accessed through the Web console. | This issue does not affect the business. You can ignore it. |
| 4 | After the inspection report language is switched, the language is not updated in time. You must manually refresh the page. | This issue does not affect the business. You can ignore it. |
| 5 | In SQL diagnostics, the SQLs filtered by the OBServer node address are displayed inaccurately. | This issue does not affect the business. You can ignore it. |
Limitations
Hardware requirements
OCP-Server can be installed on a physical server or in a Docker container. OCP-Server supports high availability deployment across multiple nodes.
The following table describes the minimum hardware requirements for OCP-Server nodes.
Hardware |
Requirements |
|---|---|
| CPU | |
| Memory | 16 GB of available memory |
| NIC | 10 GbE |
OCP-Agent consumes little resources. Therefore, no special hardware requirements are imposed on the installation node.
Operating system requirements
The following table describes the operating systems supported for installing OCP Server and 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 | 12SP3 and later |
| ARM aarch64 | AliOS | 7.2 and later |
| ARM aarch64 | NeoKylin | 7.6 |
| ARM aarch64 | Huawei EulerOS | 2.0 SP8 |
Client requirements
Most users access OCP through a Web browser. Therefore, the following table describes the client requirements.
Browser |
Minimum version |
|---|---|
| Chrome | 81 |
| Firefox | 64 |
| Safari | 10 |
| Edge | 13 |
If you want to access OCP through an iOS device, the following table describes the iOS version requirements.
Operating system |
Minimum version |
|---|---|
| iOS | 10 |
For the best user experience, we recommend that you use a display with a resolution greater than 1440 x 810.