#RNDate#2022-07-18
OceanBase Cloud Platform (OCP) is upgraded to provide improved support for the password box and inspection functionality, and is also better adapted for OceanBase Database. Other functions are also enhanced and optimized in the new version.
Version information
Version: V3.3.3
Previous version: V3.3.1
Release date: July 18, 2022
Supported upgrade path: Direct upgrade is possible from OCP V2.3.x and later. For OCP versions earlier than V2.3.0, you need to upgrade to V2.3.x first, and then to this version.
Supported OceanBase Database versions
The following table lists the OceanBase Database versions supported by OCP V3.3.2.
OceanBase V1.4.x
OceanBase V2.1.x
OceanBase V2.2.x
OceanBase V3.1.x
OceanBase V3.2.x
New features
Password box
You can import, export, and share the passwords of an OceanBase cluster or tenant that you take over.
You can share connection credentials in the password box with users in another OCP instance.
Monitoring
The Tenant Performance page of the monitoring console now displays the Memory Usage indicator, which indicates the percentage of memory consumed in an OceanBase tenant.
Security
Set Password Activation Account is supported. You need to change the password of the built-in account upon logging in to OCP for the first time.
The console no longer displays plaintext passwords, thus improving the security of the system.
Feature enhancements
OBProxy
You can modify and restart OBProxy clusters in accordance with the parameters that take effect.
Inspection
The Cluster Health Check feature is now unified under the Inspection module, and the inspection feature is further improved and optimized.
Version compatibility
OCP V3.3.2 is adapted to OceanBase V3.2.4, supporting the import of SRS data when you create a MySQL tenant.
OCP V3.3.2 is adapted to OceanBase V3.2.3.1, supporting the new rule for obtaining the kernel version number.
Issues fixed
OCP V3.3.2 fixed the following issues:
Improved the performance of some agents to enhance agent stability.
Improved the thread pool logic on the server side to enhance the performance of monitoring queries.
Improved the backup and restore acquisition process to enhance the stability of OCP when performing large-capacity backups.
Improved the real-time performance of SQL diagnostic data to enhance the speed at which OAS acquires diagnostic data.
Improved the logic for verifying the permissions of the admin account to adapt to the dedicated cloud scenario.
Improved the precheck of default directories when you create a cluster. If an error occurs during a precheck, the error is displayed before you perform a rollback.
Fixed the issue where file handles are retained in the monagent file.
Fixed the issue where an error is returned when an OCP instance cannot connect to the cluster in special scenarios.
Fixed the issue where a backup and restore task is time out.
Fixed the issue where, after an OCP instance is upgraded from a lower version (V2.x) to a higher version (V3.x), you cannot view the list of services.
Fixed the issue where, when you filter backup and restore tasks by status, no tasks are found.
Fixed the issue where an NPE error is returned when no data exists on the merge management page.
Fixed the issue where OCP V3.3.0 fails to be deployed with OAT.
Fixed some internationalization issues in inspections.
Fixed the issue where the data disk utilization is displayed as more than 100% in special scenarios.
Fixed the issue where no alert is issued for the system process utilization in abnormal scenarios.
Known issues
No. |
Known issue |
Solution |
|---|---|---|
| 1 | QPS historical data cannot be queried in special scenarios after OCP is upgraded from V3.1.x to V3.3.3. | This issue does not affect the business and can be ignored. |
| 2 | An NPE error is returned when you create a standby cluster in multi-cluster mode in special scenarios. | This issue does not affect the business and can be ignored. |
| 3 | If the user interface does not display the required data, it may request the data again. | This issue does not affect the business and can be ignored. |
| 4 | After the inspection report language is changed, the changes take effect only after you manually refresh the report. | This issue does not affect the business and can be ignored. |
| 5 | When you filter SQL statements by the IP addresses of the OBServer nodes in SQL diagnostics, the filter results are inaccurate. | This issue does not affect the business and can be ignored. |
Limitations
Hardware requirements
OCP-Server can be installed on physical servers, or deployed in Docker containers. OCP-Server supports a multi-node high availability deployment mode.
The following table lists the minimum hardware requirements for OCP-Server nodes.
Hardware |
Requirements |
|---|---|
| CPU | |
| Memory | 16 GB available memory |
| Network interface card | 10-Gbps NIC |
OCP-Agent occupies very little resources and has no specific hardware requirements for installation nodes.
Operating system requirements
The following table lists the operating systems supported by OCP Server (which contains 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
Most users access OCP through Web browsers. The following table lists the supported browsers and their minimum versions.
Browser |
Minimum version |
|---|---|
| Chrome | 81 |
| Firefox | 64 |
| Safari | 10 |
| Edge | 13 |
The following table lists the operating systems and their minimum versions supported when you use an iOS device to access OCP.
Operating system |
Minimum version |
|---|---|
| iOS | 10 |
To ensure the best user experience, we recommend that you use a display with a screen resolution of more than 1440 x 810.