OCP V3.3.0

The new version of OceanBase Cloud Platform (OCP) primarily upgrades the SQL diagnostics feature and introduces rich capabilities such as primary/standby database decoupling, while also optimizing other features in detail.

Version information

• Version: V3.3.0

• Previous version: V3.2.3

• Release date: April 27, 2022

• 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

OCP V3.3.0 supports the OceanBase Database versions listed in the following table.

• OceanBase V1.4.x

• OceanBase V2.1.x

• OceanBase V2.2.x

• OceanBase V3.1.x

• OceanBase V3.2.x

New features

Diagnostics

• Transaction diagnostics

  Long-running and suspended transactions on the call chain can occupy certain resources for extended periods without releasing them, causing the system to become unstable and affecting its ability to provide efficient services. Transaction diagnostics provides monitoring and analysis of transactions, offering details, Execution Information, and Details About Executed SQL Statements to understand the transaction model and identify the specific reasons for time or resource consumption.

  Additionally, OCP provides emergency measures for abnormal transactions. You can close abnormal transactions with one click to help the system quickly return to a stable state.

• Correlation analysis

  While adding more diagnostic dimensions (transaction diagnostics, AP SQL diagnostics, SQL request analysis), it also supports correlation analysis between alerts, monitoring, transactions, SQL, and traces.

• SQL Request Analysis

  Building upon existing SQL diagnostics capabilities, SQL request analysis is added to analyze the execution of all database requests from a database/SQL perspective. This includes execution time distribution, the proportion of various SQL types, and execution trends. It helps you gain a more comprehensive understanding of SQL execution and enables you to quickly detect any anomalies during SQL execution.

• Parallel SQL Execution Profile

  Enhanced the analysis and diagnostic capabilities of SQL diagnostics for OLAP-type SQL. In complex SQL scenarios such as distributed queries, parallel queries, multi-table joins, and AP, it helps you identify specific slow operators or steps during SQL execution, accelerating the SQL tuning process.

  • The following figure shows the parallel SQL execution profile in offline mode.

  • The following figure shows the parallel SQL execution profile in online mode.

• Custom Columns

  The SQL diagnostics feature supports custom columns and advanced condition filtering.

• SQL Optimization Suggestions

  Currently, SQL diagnostics already has strong anomaly detection capabilities. It can detect the presence of SlowSQL and suspicious SQL based on expert experience. Additionally, SQL diagnostics provides practical emergency measures, including SQL throttling and binding plans/indexes. However, for abnormal SQL detected by the system, you need to decide how to perform emergency operations yourself. SQL optimization suggestions are designed to guide (recommend) how to perform SQL tuning.

  Currently, OCP supports recommendations for creating optimal indexes, historical execution plans, and tenant CPU scaling, guiding and helping you resolve SQL issues more quickly.

• Deadlock Detection

  Deadlock detection provides detailed information about deadlocks, including the roles of deadlock participants, the execution order in which the deadlock occurs, and the SQL statements executed by the deadlock nodes. This helps you analyze the root cause of the deadlock and performs real-time analysis of circular dependencies to resolve them.

• Emergency Response

  Building upon the previous execution plan binding, it provides emergency response capabilities for single SQL and batch SQL throttling.

Primary and standby databases

• Decoupling of primary and standby databases

  Supports physical splitting of primary and standby databases, allowing the standby database to be independently promoted to a primary database. This facilitates production environment drills and stress testing for business operations.

• The original primary database starts in read-only mode after failover

  To facilitate data verification and migration to the new primary database, OCP supports starting the abandoned primary database in read-only mode after a disaster recovery operation. After the original primary cluster is started as a read-only cluster following a failover, you can compare and correct data between the new primary cluster and the original primary cluster.

Alerts

Supports custom alerts, allowing monitoring metrics to be easily converted into alert information.

Capacity management

A replica view has been added to the cluster Resource Management page, where you can view the distribution of replicas.

Backup and recovery

Supports tenant-level backup, allowing you to perform snapshot backups for tenants.

Feature enhancements

• Enhanced alert functionality: Supports custom alert metrics, allowing monitoring metrics to be easily converted into alert information, and supports configuring alerts for slow SQL.

• Enhanced organizational permission management: You can group all resources under one organization as needed, facilitating resource management and identification.

• Improved the cluster Performance Monitoring feature: Added statistics display for Block Cache Size, Cache Hit Rate, Number of Cache Requests, and Number of Open Cursors in performance monitoring.

• Enhanced the data mid-end: Logs collected by ocp-agent from OBServer nodes, OBProxy, etc., are written to storage platforms such as ES/SLS, providing comprehensive log query capabilities and laying a solid data foundation for more advanced log analysis capabilities.

Fixed issues

OCP V3.3.0 fixes the following issues:

• Agent reinstallation failure in specific scenarios.

• Tenant data deletion during rollback or retry during OceanBase upgrades.

• "OBProxy parameter version inconsistent with cluster parameter version. Please refresh the configuration" error on the OBProxy configuration page in specific scenarios.

• OBProxy process startup failure in specific scenarios.

• Fixed the issue where host status is displayed incorrectly in specific scenarios.

• Fixed the issue where an error occurs during software package sorting.

• Fixed the issue where tenant names are displayed incorrectly in cluster performance reports under specific circumstances.

• Fixed the issue where a large number of temporary log files remain due to a Logback component bug.

• Fixed the issue where SQL diagnostics cannot query data under specific scenarios.

• Fixed the issue where the OCP frontend responds extremely slowly and the CPU usage of the ocp-server container remains high.

Known issues

Version requirements

Hardware requirements

OCP-Server can be installed on physical servers or run in Docker containers. OCP-Server supports multi-node high-availability deployment.

The minimum hardware requirements for an OCP-Server node are listed in the following table.

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.

Client requirements

Users typically access OCP services through a web browser. The client requirements are as follows.

If you need to access OCP from a device running iOS, the version requirements are listed in the following table.

For the best user experience, we recommend using a display with a resolution greater than 1440 × 810.