#RNDate#2022-07-18
The current new version of the OceanBase Cloud Platform (OCP) is mainly upgraded for the encryption box, inspection feature, and compatibility with the OceanBase version, as well as other features are also optimized.
Version information
Version: V3.3.3
Version: V3.3.1
Version release date: July 18, 2022
Supported upgrade path: You can directly upgrade OCP V2.3.x and later versions to this version. If you have an OCP version earlier than V2.3.0, first upgrade it to OCP V2.3.x and then upgrade it to this version.
Supported OceanBase Database versions
The following table describes the supported OceanBase Database versions in OCP V3.3.2.
OceanBase V1.4.x
OceanBase V2.1.x
OceanBase V2.2.x
OceanBase V3.1.x
OceanBase V3.2.x
What's new?
Safe
Support import, export, and sharing of cluster passwords and tenant passwords for assumed clusters.
Ability to share the connection credentials in the password box with other OCP users.
Monitoring
The Memory Usage indicator is added to the Tenant Performance Monitoring page. The indicator specifies the percentage of memory that is used by the tenants of OceanBase Database.
Security
Added the Set Password to Activate Account feature. When you first log in to OCP, you need to modify the password of the built-in account.
In the browser console, remove the prompt about plain passwords to enhance system security.
Feature Enhancements
OBProxy
The following table lists the parameters that take effect after the restart of an ODP service.
Patrol
Unified the Inspection feature under the Inspection module and improved the inspection feature.
Version compatibility
Adapts to OceanBase Database V3.2.4 and supports importing SRS data when a MySQL tenant is created.
OceanBase Database V3.2.3.1 is now supported. The way to obtain the kernel version has been adapted to the new rules.
Fixed Issues
OCP V3.3.2 fixed the following issues:
Improve agent performance and stability
Optimized Server end thread pool logic to improve monitoring query performance.
Optimize backup and restore data collection process to improve OCP stability for large volume backup.
Improve the real-time availability of SQL diagnostic data and enhance the speed at which OAS retrieves diagnostic data.
Optimize the permission validation logic for the admin account to adapt to the private cloud scenario.
Optimize the pre-check process for the default directory creation when you create a cluster. This allows errors to be exposed early in case of issues, preventing the need to roll back the entire task.
Fixed the problem where mOnagent files left residual file handles.
Fixed the issue where a cluster cannot connect in special scenarios.
Fixed the issue with backup recovery scheduling timeout.
Fixed an issue where you cannot view the service list after upgrading from a lower version (V2.x) to a higher version (3.x).
Fixed an issue where the filter by status fails during backup and restore.
Fix the NPE when there is no data in the merge management page.
Fixes the issue where OCP V3.3.0 cannot be deployed by using OAT.
Fixed some internationalization issues for the inspections.
Fixed the issue where the data disk utilization displayed exceeding 100% in specific scenarios.
Fixed a problem where CPU sys usage could not trigger an alert in abnormal conditions.
Known issues
Issue |
Known Issues |
Workarounds |
|---|---|---|
| 1 | After upgrading from V3.1.x to V3.3.3, specific cases may result in the inability to query QPS historical data. | Currently, this does not affect business operations and does not require avoidance. |
| 2 | NPE in multi-cluster mode when creating a standby cluster in abnormal scenarios. | No business impact. No workaround is required. |
| 3 | Some interfaces will be requested twice if accessed through the interface. | This does not affect business operations and can be ignored for now. |
| 4 | After you change the language on the inspection reports, the change does not take effect until you manually refresh the page. | This does not affect your business, so no workaround is required. |
| 5 | Filter SQL statements in the SQL diagnostics based on the OBServer node IP address. The filtered SQL results are inaccurate. | This does not affect the business, and no workaround is needed. |
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 lists the minimum hardware requirements for an OCP-Server node.
Hardware |
Requirements |
|---|---|
| CPU | |
| Memory | 16 GB available memory |
| NIC | 10G NIC |
OCP-Agent occupies few resources and has no specific requirements for the hardware resources of the installation nodes.
OS requirements
The table below lists the operating system requirements for installing the OCP service (with OCP-Agent).
Server Type |
Operating System |
Supported Version |
|---|---|---|
| x86_64 | RHEL | 7.2 or later |
| x86_64 | CentOS | 7.2 and later |
| x86_64 | AliOS | 7.2 and later versions |
| x86_64 | openSUSE | 12SP3 and later |
| ARM aarch64 | AliOS | 7.2 or later |
| ARM aarch64 | NeoKylin | 7.6 |
| ARM aarch64 | Huawei EulerOS | 2.0 SP8 |
Client requirements
In general, users access OCP services through web browsers. Therefore, the following requirements apply to the client-side:
Browser |
Minimum Version |
|---|---|
| Chrome | 81 |
| Firefox | 64 |
| Safari | 10 |
| Edge | 13 |
If you want to access OCP via an iOS device, the minimum system requirements are as follows:
Operating System |
Minimum Version |
|---|---|
| iOS | 10 |
For optimal use, we recommend using a display with a resolution higher than 1440 x 810.