The new version of OceanBase Cloud Platform (OCP) primarily upgrades the password box and inspection features, adapts to the OceanBase version, and enhances and optimizes other functionalities.
Version information
Version: V3.3.3
Previous version: V3.3.1
Release date: July 18, 2022
Supported upgrade path: You can directly upgrade from OCP V2.3.x and later versions to this version. For versions earlier than OCP V2.3.0, you must first upgrade to V2.3.x and then to this version.
Supported OceanBase Database versions
OCP V3.3.2 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
Password box
Supports importing, exporting, and sharing cluster or tenant passwords for over taken clusters.
Supports sharing connection credentials from the password box with other OCP users.
Monitoring
The tenant performance monitoring page adds the Memory Usage metric, which displays the percentage of memory used by the tenant on the OceanBase side.
Security
Added the Set password to activate account feature. You must change the password of the built-in account upon initial login to OCP.
Removed the plaintext password prompt from the browser console to enhance system security.
Feature enhancements
OBProxy
Supports modifying parameters that take effect upon restart for an OBProxy cluster.
Inspection
Unified the Cluster Health Inspection feature under the Inspection module, improving and optimizing the inspection functionality.
Version adaptation
Adapted for OceanBase V3.2.4, supporting the import of SRS data when creating a MySQL-compatible tenant.
Adapted for OceanBase V3.2.3.1, updating the kernel version retrieval rule.
Bug fixes
OCP V3.3.2 fixes the following issues:
Optimized performance and stability of several Agents.
Optimized server-side thread pool logic to improve monitoring query performance.
Optimized the backup and recovery collection process to enhance OCP's stability under large-scale backups.
Improved the real-time nature of SQL diagnostic data, speeding up the diagnostic data retrieval in OAS.
Optimized the permission verification logic for the admin account to better suit private cloud scenarios.
Improved the pre-check process for the default directory during cluster creation, allowing errors to be detected early if present and avoiding task rollback.
Fixed the issue of residual file handles by monagent.
Fixed the issue of reported cluster connection failures in special scenarios.
Fixed the issue of backup and recovery scheduling timeouts.
Fixed the issue where the service list could not be viewed after upgrading backup and recovery from a lower version (V2.x) to a higher version (3.x).
Fixed the issue of failed filtering of backup and recovery by status.
Fixed the issue of NPE reported on the major compaction management page when no data was available.
Fixed the issue of failed deployment of OCP V3.3.0 using OAT.
Fixed some internationalization issues with inspections.
Fixed the issue where data disk usage exceeded 100% under specific circumstances.
Fixed the issue where there was no alert for high CPU sys utilization under abnormal conditions.
Known issues
Number |
Known issues |
Workaround |
|---|---|---|
| 1 | Querying QPS historical data fails in specific scenarios after upgrading from V3.1.x to V3.3.3 | If your business is not currently affected, you may not need to take any action. |
| 2 | NPE Reported When Creating a Standby Cluster in Multi-Cluster Mode in Non-Conventional Scenarios | If your business is not currently affected, you may not need to take any action. |
| 3 | Some APIs are requested twice consecutively when accessed through the console. | If your business is not currently affected, you may not need to take any action. |
| 4 | The language of the inspection report does not take effect immediately after switching. You need to manually refresh the page. | If your business is not currently affected, you may not need to take any action. |
| 5 | SQL diagnostics filter SQL statements by OBServer node address, but the filter results are inaccurate. | If your business is not currently affected, you may not need to take any action. |
Version requirements
Hardware requirements
OCP-Server can be installed on physical servers or run in Docker containers. OCP-Server supports multi-node high-availability deployment.
The minimum hardware requirements for an OCP-Server node are listed in the following table.
Hardware |
Requirements |
|---|---|
| CPU | |
| Memory | Available Memory: 16 GB |
| NIC | 10 Gbit/s NIC |
OCP-Agent consumes very few resources and has no specific hardware requirements for the installation node.
Operating system requirements
The operating system requirements for installing the OCP server (including OCP-Agent) are listed in the following table.
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
Users typically access OCP services through a web browser. The client requirements are as follows.
Browser |
Minimum Version |
|---|---|
| Chrome | 81 |
| Firefox | 64 |
| Safari | 10 |
| Edge | 13 |
If you need to access OCP from a device running iOS, the version requirements are listed in the following table.
Operating System |
Minimum Version |
|---|---|
| iOS | 10 |
For the best user experience, we recommend using a display with a resolution greater than 1440 x 810.