#RNDate#2021-12-27
OceanBase Cloud Platform (OCP) V3.2.3 introduces the ability to query logs through a graphical interface and parameter templates. It also features significant updates in monitoring and alerting capabilities. Performance monitoring now supports drill-down analysis, with detailed performance metrics for comprehensive business understanding. SQL diagnostics allow setting SQL throttling, plan binding, and query binding history. Performance reports now include statistics on PRC, memory, and parameter configuration changes. The alerting feature now supports multiple thresholds and includes 10 new built-in alerts to enhance OCP's operational capabilities for OceanBase clusters.
Version information
Version: V3.2.3
Previous Version: V3.1.5
Date of release: December 27, 2021
Supported upgrade path: Direct upgrade from OCP V2.3.x and later is supported. Upgrades from OCP versions earlier than V2.3.0 require first upgrading to V2.3.x before upgrading to this version.
Supported OceanBase Database versions
OceanBase Cloud V3.2.3 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
Drill down the Performance Monitoring for clusters and tenants.
By using the drill-down feature, you can directly view the metrics for a specified tenant or OBServer node in the tenant or OBServer node page without needing to manually switch to the Performance Monitoring page of the tenant or the Monitoring tab of the host.
The query feature for logs is provided, which allows you to set search conditions in the OCP console and view the logs you need. The query feature covers logs of OBServer, OBProxy, and hosts. You can quickly search for logs without downloading them.
SQL Diagnostics supports binding indexes, plan binding, and throttling for SQL, as well as querying bind history on the SQL details page.
Added 10 new built-in alert types to monitor and alert for metrics such as active sessions, CLog synchronization latency, and OCP cross-cloud control. It now supports multiple threshold alerting, offering more reliable performance and stability assurance for OceanBase clusters.
Support for template parameter creation. You can create parameter templates and apply these templates when you create a tenant or a cluster. This can help you avoid repeatedly configuring parameters when you create a tenant or a cluster.
For information about how to create a template, see Cluster parameter templates.
To create a cluster or a tenant, see Create a cluster and Create a tenant.
Enhancements
Enhanced the performance monitoring functionality by further subdivide the metrics for clusters and tenants. These metrics include:
Cluster: QPS, Query response time, TPS, Transaction response time.
Tenant: Waiting Request Queue , Transactions per second (TPS), and Transaction Response Time
Optimizes and enhances the logic for upgrading and restarting OBServer nodes, supporting scheduled maintenance upgrades and restarts. This optimization allows you to quickly upgrade and restart OBServer nodes without requiring business continuity.
Enhance the Performance Report feature. Performance reports now show new statistics including Memory, RPC, and Parameter Changes.
Fixes
The OceanBase Cloud platform version V3.2.3 fixes the following issues:
Resolved incomplete SQL diagnostic collection and slow front-end loading issues.
Data loss in performance reports.
Task retry and abandon exceptions after failure.
Known Issues
ID |
Known Issue |
Workaround |
|---|---|---|
| 1 | OCP 2.4 does not support host password credential storage. | When upgrading to OCP 2.4, add the host password box password to OCP and reinstall all ocp_agent. |
| 2 | During the password change process of proxyro, make sure that all OCP clusters, OceanBase clusters, and OBProxy are available, otherwise the operation will be blocked. | During the password change process of proxyro, make sure that all OCP clusters, OceanBase clusters, and OBProxy are available. |
| 3 | OceanBase cluster 2.3.x is upgraded to a 3.2.x cluster without display issue. | Manually enter cluster architecture information. |
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 minimum hardware requirements for OCP-Server nodes are shown in the following table.
Hardware |
Requirements |
|---|---|
| CPU | |
| Memory | 16 GB of available memory |
| NIC | 10 GbE NIC |
OCP-Agent consumes very little resources and has no special requirements for the installation node's hardware.
Operating system requirements
The following table shows the operating system requirements for installing OCP-Server (including OCP-Agent).
Server Type |
Operating System |
Supported Version |
|---|---|---|
| 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 access OCP services through a web browser, so the following client requirements apply.
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 shows the requirements.
Operating System |
Minimum Version |
|---|---|
| iOS | 10 |
For the best user experience, we recommend that you use a display with a resolution of more than 1440 x 810.