#RNDate#2021-12-27
OceanBase Cloud Platform V3.2.3 introduces a new feature for visual log querying and parameter template management. Additionally, the platform undergoes significant updates in monitoring and alerting capabilities. The new performance monitoring feature includes drill-down analysis and detailed metrics for comprehensive business analysis. SQL diagnostics now support SQL throttling settings, plan binding, and query binding history tracking. Performance reports now include statistical information on PRC, memory, and parameter configuration changes. The alerting feature in this version supports multiple thresholds and includes 10 new built-in alerts to enhance OCP's operational capabilities for OceanBase clusters.
Version information
Version number: V3.2.3
Previous version: V3.1.5
Date of release: 2021 December 27
Supported upgrade path: You can directly upgrade OCP V2.3.x or later versions to this version. If the source version is earlier than V2.3.0, you must first upgrade to V2.3.x and then upgrade 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
The Performance Monitoring feature supports drill-down analysis for metrics.
You can drill down the metric in the tenant node or observer node dimensions to view metric data without switching to the Performance Monitoring tab on the tenant details page or to the Monitoring tab on the host details page.
New log query feature: You can set query conditions on the OCP console to query logs of various types, including those of the OBServer nodes, OBProxy, and host. You do not need to download the logs.
The SQL diagnosis feature supports binding indices, plan binding, SQL throttling, and querying binding history for SQL statements on their detail pages.
New built-in alert items are added, providing comprehensive monitoring and early warning capabilities for metrics such as the number of active sessions, CLog synchronization delay, and cross-cloud management in OceanBase Cloud. Alerts support multiple threshold settings, enhancing the performance and stability of OceanBase clusters.
The parameter template feature is now available. If you need to create multiple tenants or clusters with the same configurations, you can first create a parameter template and then apply it when you choose Create Tenant or Create Cluster. This will avoid the need to reconfigure the parameters of the clusters or tenants each time you choose Create Cluster or Create Tenant.
For information about how to create a template, see Cluster parameter templates.
To create a cluster or tenant, see Create a cluster or Create a tenant.
Feature enhancements
Enhanced the performance monitoring feature. It further refines metrics to help you view more detailed performance information about the clusters and tenants. The following metrics are available:
Cluster: QPS , Query response time , TPS , Transaction response time .
Tenant: request wait queue , TPS , transaction response time .
Optimized the logic for upgrading and restarting an OBServer node to support scheduled maintenance upgrades and restarts. This change allows you to upgrade and restart OBServer nodes without service continuity requirements.
Enhanced the Performance Report feature of the cluster, supporting the display of statistics including Memory, RPC, and Parameter Changes.
Fixed Issues
The following issues were fixed in OceanBase Cloud V3.2.3:
Incomplete SQL diagnostics collection and slow frontend loading.
Some data was missing from performance reports.
Retry and abandon tasks that fail.
Known issues
Number |
Known issues |
Mitigation |
|---|---|---|
| 1 | OCP 2.4 does not store host password credentials. | During OCP 2.4 upgrade, the host password vault password is added to OCP, and all ocp_agent must be reinstalled. |
| 2 | During the process of changing the proxyro password, ensure that all OCP clusters, OceanBase clusters, and OBProxy instances are available; otherwise, it may be stuck. | During the process of changing the proxyro password, make sure that all OCP clusters, OceanBase clusters, and OBProxy instances are available. |
| 3 | An architecture issue is not displayed when you upgrade an OceanBase Database 2.3.x cluster to a 3.2.x cluster. | Manually specify the cluster architecture. |
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 |
Requirements |
|---|---|
| CPU | |
| Memory | 16 GB available memory |
| NIC | 10 GbE NIC |
OCP-Agent consumes very few resources and does not have 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 | 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 web browsers. The following table lists the requirements for clients.
Browser |
Minimum Version |
|---|---|
| Chrome | 81 |
| Firefox | 64 |
| Safari | 10 |
| Edge | 13 |
If you want to access OCP services on an iOS device, the operating system must meet the requirements listed in the following table.
Operating System |
Minimum Version |
|---|---|
| iOS | 10 |
For the best user experience, we recommend that you use a display with a resolution greater than 1440 x 810.
