The OceanBase Cloud Platform (OCP) V3.2.3 provides a new feature: the visual log query feature and parameter templates. In terms of monitoring and alerts, the version also implements breakthrough updates. The performance monitoring feature allows for drill-down analysis and provides granular performance metrics to help you comprehensively understand and analyze your business. The SQL diagnostics feature supports setting SQL throttling, plan binding, and query binding history. The performance reports include statistics on PRC, memory, and parameter configuration changes. In terms of alerts, the version not only supports multi-threshold alerts but also introduces 10 built-in alerts to enhance OCP's maintenance capabilities for OceanBase clusters.
Version information
Version: V3.2.3
Prerequisites: V3.1.5
Version Released: 2021-12-27
**Supported upgrade path: ** For OCP V2.3.x and later, you can directly upgrade to this version. For OCP V2.3.0 and earlier, you must first upgrade to V2.3.x and then to this version.
Supported OceanBase Database versions
OceanBase Cloud V3.2.3 supports the following versions of OceanBase Database:
OceanBase V1.4.x
OceanBase V2.1.x
OceanBase V2.2.x
OceanBase V3.1.x
OceanBase V3.2.x
New features
Performance Monitoring supports drilling down into metric data for clusters and tenants.
By using the drilldown feature, you can directly drill down to the tenant or OBServer node level to view the metric data without the need to navigate through the complex path to the Performance Monitoring page of the tenant or the Monitoring tab of the host.
Added the log query feature. You can use this feature to set query conditions on the OCP console and view the required logs. This feature supports querying logs for all types of resources, including OBServer nodes, OBProxy, and hosts. This feature allows you to easily perform log retrieval without download logs.
SQL diagnostics support SQL index binding, plan binding, SQL throttling, and query history for SQL in the details page.
Add 10 built-in alert items, enabling full monitoring and early warning for metrics such as the number of active sessions, log synchronization delay, and cross-cloud control in OCP. Alerts now support multiple thresholds, providing even stronger assurance for the performance and stability of OceanBase clusters.
Parameter templates are now supported. If you need to create multiple tenants or clusters with the same settings, you can first create a parameter template and then apply it when you click Create Tenant or Create Cluster. This way, you won't have to configure the parameters of the cluster or tenant again when you click Create Cluster or Create Tenant.
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.
Feature enhancements
Enhance the Performance Monitoring feature to further segment cluster and tenant-related metrics, providing you with more detailed performance information. These metrics include:
Cluster: QPS , Query Response Time , TPS , Transaction Response Time .
Tenants: Request Wait Queue , TPS , Transaction Response Time .
Optimized and restarted OBServer nodes to support the offline upgrade and offline restart of OBServer nodes. This optimization allows you to upgrade and restart OBServer nodes without requiring continuous availability.
Improve the Performance Report feature by adding statistics for Memory, RPC, and Parameter Changes.
Fixed Issues
OceanBase Cloud V3.2.3 addresses the following issues:
Resolves the issue of incomplete SQL diagnostics and slow frontend loading.
Data loss in performance report.
Retrying and abandoning exception problems after a task fails.
Known issues
# |
Known issues |
Workarounds |
|---|---|---|
| 1 | Host credentials are not stored in OCP 2.4. | When upgrading to OCP 2.4, you need to add host password vault credentials to OCP and then reinstall all ocp_agent. |
| 2 | When you change the password of the proxyro user, make sure that all OCP clusters, OceanBase Database clusters, and OBProxy services are accessible. Otherwise, it will get stuck. | When you change the password of the proxyro user, make sure that all OCP clusters, OceanBase Database clusters, and OBProxy services are accessible. |
| 3 | OceanBase 2.3.x clusters can be upgraded to the 3.2.x cluster architecture. | Manually fill in the 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 following table lists the minimum hardware requirements for OCP-Server nodes.
Hardware |
Requirement |
|---|---|
| CPU | |
| Memory | 16 GB of available memory |
| NIC | 10 GbE NIC |
OCP-Agent consumes very few resources and has no special requirements for the hardware resources of the installation node.
Operating system requirements
The following table lists 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 | 12SP3 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 web browsers. The following table lists the client requirements.
Browser |
Minimum version |
|---|---|
| Chrome | 81 |
| Firefox | 64 |
| Safari | 10 |
| Edge | 13 |
If you need to access OCP services from an iOS device, the following table lists 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.