OCP V3.3.0

OceanBase Cloud Platform (OCP) is upgraded to support SQL diagnostics and introduces new features such as decoupling of primary and standby databases. Other features are also optimized.

Version information

• Version: V3.3.0

• Previous version: V3.2.3

• Version release date: April 27, 2022

• Supported upgrade path: You can directly upgrade OCP V2.3.x and later versions to this version. If you want to upgrade an OCP version earlier than V2.3.0, you must first upgrade it to V2.3.x and then upgrade it to this version.

Supported OceanBase Database versions

OCP V3.3.0 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

Diagnostics

• Transaction diagnostics

  Long-running or hanging transactions in a call chain can occupy resources for a long time, leading to an unstable system state and affecting the system's ability to provide efficient services. Transaction diagnostics provides monitoring and analysis of transactions, along with Execution Information and Details About Executed SQL Statements to identify the root causes of resource consumption or performance issues.

  OCP also provides an emergency response by allowing you to disable problematic transactions with a single click, helping the system quickly return to a stable state.

  

• Correlation analysis

  In addition to transaction diagnostics, AP SQL diagnostics, and SQL request analysis, OCP now supports correlation analysis between alerts, monitoring data, transactions, SQL statements, and traces.

  

• SQL request analysis

  SQL request analysis provides insights into all database requests from the Execution Information perspective, including execution time distribution, SQL type distribution, and execution trends. This helps you comprehensively understand SQL execution and quickly identify any anomalies during execution.

  

• Parallel SQL execution profiling

  OCP enhances SQL diagnostics for OLAP-type SQL, enabling you to identify slow operators or steps in complex SQL scenarios such as distributed queries, parallel queries, multi-table joins, and AP queries. This accelerates SQL optimization.

  

  • Offline parallel SQL execution profiling:

    

  • Online parallel SQL execution profiling:

    

• Custom columns

  SQL diagnostics now supports custom columns and advanced condition filtering.

  

• SQL optimization suggestions

  SQL diagnostics can detect SlowSQL and suspicious SQL based on expert experience. It also provides emergency response measures such as SQL throttling and plan/index binding. However, you need to determine how to handle the detected SQL. SQL optimization suggestions guide you on how to optimize SQL.

  OCP now supports recommendations for optimal index creation, historical execution plan recommendations, and tenant CPU expansion recommendations to help you quickly resolve SQL issues.

  

• Deadlock detection

  Deadlock detection provides detailed information about deadlocks, including the roles of the participants, the execution order, and the SQL statements involved. This helps you analyze the root causes of deadlocks and resolve them by analyzing and addressing cyclic dependencies.

  

• Emergency response

  In addition to binding execution plans, OCP now supports emergency response measures such as throttling individual or batch SQL statements.

Primary and standby databases

• Decoupling of primary and standby databases

  OCP allows you to physically split primary and standby databases, promoting the standby database to a primary database. This facilitates production environment testing and load testing.

  

• Read-only mode for the original primary database after failover

  OCP supports starting the original primary database in read-only mode after a failover. This allows you to verify and migrate data from the new primary database to the original primary database.

Alerts

You can now customize alerts and convert simple monitoring metrics into alert information.

Capacity management

The Resource Management page of a cluster now includes a replica view, allowing you to view the distribution of replicas.

Backup and restore

OCP now supports tenant-level backups, allowing you to create snapshots of tenants.

Feature enhancements

• Enhanced alerting capabilities: You can now customize alert metrics and convert simple monitoring metrics into alert information. You can also configure alerts for slow SQL.

• Enhanced organization management: You can now organize all resources into a single organization for easier management and identification.

• Enhanced cluster Performance Monitoring: Performance monitoring now includes statistics on Block Cache Size, Cache Hit Rate, Number of Cache Requests, and Number of Open Cursors.

• Enhanced data middleware: OCP-agent now collects logs from OBServer nodes and OBProxy and writes them to storage platforms such as ES and SLS. This provides comprehensive log query capabilities and lays the foundation for advanced log analysis.

Fixed issues

OCP V3.3.0 fixes the following issues:

• The issue where agent fails to reinstall in specific scenarios.

• The issue where tenant data may be deleted during rollback or retry during OceanBase upgrade.

• The issue where the OBProxy configuration page displays "The parameter version of OBProxy does not match that of the cluster. Please refresh the configuration" in specific scenarios.

• The issue where OBProxy processes are restarted repeatedly in specific scenarios.

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

• The issue where an error is returned when sorting software packages.

• The issue where the tenant name is displayed incorrectly in specific scenarios in the cluster performance report.

• The issue where a large number of tmp log files are left behind due to a bug in the logback component.

• The issue where SQL diagnostics cannot query data in specific scenarios.

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

Known issues

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 as follows:

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 services (including OCP-Agent).

Client requirements

General users access OCP services through web browsers. The following table lists the client requirements.

If you want to access OCP services on an iOS device, the operating system requirements are as follows:

For the best user experience, we recommend that you use a display with a resolution greater than 1440 x 810.