OceanBase Cloud Platform (OCP) V3.2.3 introduces new features including log query on the web interface and parameter templates. It also brings significant updates to monitoring and alerting. Performance monitoring now supports drill-down analysis, and some performance metrics have been subdivided to help you understand and analyze your business more comprehensively. SQL diagnostics support setting SQL throttling, plan binding, and binding history queries. Performance reports have added statistics display for PRC, memory, and parameter configuration changes. The alerting feature not only supports multiple thresholds but also includes 10 built-in alerts to enhance OCP's operational capabilities for OceanBase clusters.
Version information
Version: V3.2.3
Previous version: V3.1.5
Release date: December 27, 2021
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
OceanBase Cloud Platform 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
The Performance Monitoring section for clusters and tenants now supports drill-down analysis.
With the drill-down feature, you can directly go down to the tenant or OBServer node dimension to view the data of the metric at that dimension, without having to switch through complex paths to the tenant's Performance Monitoring page or the host's Monitoring tab.
A new log query feature is available. You can use this feature to set query conditions on the OCP interface to view the logs you need. The query scope covers all types of logs, including those on OBServer nodes, OBProxies, and hosts. This allows you to easily search for logs without downloading them.
The SQL diagnostics feature supports binding indexes, plans, and setting SQL throttling for an SQL statement on its details page, as well as binding its historical queries.
Ten built-in alert items are added, providing comprehensive monitoring and early warning for active session count, clog synchronization latency, and cross-cloud management of OCP. Additionally, alerts support multiple thresholds, providing a stronger guarantee for the performance and stability of OceanBase clusters.
A new parameter template feature is introduced. If you need to create multiple tenants or clusters with the same configuration, you can first create a parameter template and then apply it when creating a Create Tenant or Create Cluster. This avoids repeating the cluster/tenant parameter configuration when creating a cluster or tenant.
Feature enhancements
The performance monitoring feature has been optimized. Relevant metrics for clusters and tenants have been further subdivided to provide you with more detailed performance information. These metrics include:
Cluster: QPS, Query response time, TPS, Transaction response time.
Tenant: Request waiting queue, TPS, Transaction response time.
The logic for upgrading and restarting OBServer nodes has been optimized to support stopping and then upgrading or restarting OBServer nodes. This optimization meets your requirement for quickly upgrading and restarting OBServer nodes when business continuity is not a concern.
The cluster Performance Report feature has been improved. The performance report now includes statistics for Memory, RPC, and Parameter Changes.
Bug fixes
OceanBase Cloud Platform V3.2.3 fixes the following issues:
Incomplete SQL diagnostics collection and slow frontend loading.
Data loss in the performance report.
Abnormal retry and abort behavior after a task fails.
Known issues
Number |
Known issues |
Workaround |
|---|---|---|
| 1 | OCP 2.4 does not save host password credentials. | During the OCP 2.4 upgrade, you need to add the host password box password to OCP and then reinstall all ocp_agent. |
| 2 | During the process of changing the proxyro password, ensure that all OCP clusters, OceanBase clusters, and OBProxy instances are available; otherwise, the operation may get stuck. | During the process of changing the proxyro password, ensure all OCP clusters, OceanBase clusters, and OBProxy instances are available. |
| 3 | The issue where the cluster architecture is not displayed when upgrading an OceanBase cluster from version 2.3.x to 3.2.x has been resolved. | Manually enter the cluster architecture information. |
Version usage limitations
Hardware requirements
OCP-Server can be installed on physical servers or run in Docker containers. OCP-Server supports high-availability deployment across multiple nodes.
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 as follows.
Operating System |
Minimum Version |
|---|---|
| iOS | 10 |
For the best user experience, we recommend using a display with a resolution greater than 1440 x 810.