OCP V3.3.0

#RNDate#2022-04-27

OceanBase Cloud Platform (OCP) is upgraded to support more features, such as SQL diagnostics and decoupling of primary and standby databases, and other features are 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 to this version. If you are using OCP V2.3.0 or earlier, you must first upgrade to V2.3.x before upgrading 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 and hanging transactions in the call chain can occupy resources for a long time, leading to system instability and affecting the efficient operation of the system. Transaction diagnostics provides monitoring and analysis of transactions, along with detailed information, Execution Information, and Details About Executed SQL Statements, to identify the specific reasons for time or resource consumption in transactions.

  Additionally, OCP provides emergency measures for abnormal transactions, allowing you to disable them with a single click to help the system quickly return to a stable state.

  

• Correlation analysis

  In addition to the new diagnostic dimensions (transaction diagnostics, AP SQL diagnostics, and SQL request analysis), OCP also supports correlation analysis between alerts, monitoring, transactions, SQL, and traces.

  

• SQL request analysis

  In addition to SQL diagnostics, OCP now provides SQL request analysis from the database/SQL perspective. This analysis covers execution time distribution, the proportion of different SQL types, and execution trends. This helps you gain a comprehensive understanding of SQL execution and quickly identify any anomalies during execution.

  

• Parallel SQL execution profiling

  OCP enhances the analysis and diagnostics capabilities for OLAP-type SQL. In complex SQL scenarios such as distributed queries, parallel queries, multi-table joins, and AP queries, it helps you identify slow operators or steps in SQL execution, accelerating SQL optimization.

  

  • Offline parallel SQL execution profiling is shown in the following figure.

    

  • Online parallel SQL execution profiling is shown in the following figure.

    

• Custom columns

  In SQL diagnostics, you can now define custom columns and apply advanced condition filters.

  

• SQL optimization suggestions

  SQL diagnostics now has strong anomaly detection capabilities, including the ability to detect SlowSQL and suspicious SQL based on expert experience. It also provides practical emergency measures such as SQL throttling and plan/index binding. However, for system-detected abnormal SQL, you need to determine the appropriate emergency actions. 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, helping you quickly resolve SQL issues.

  

• Deadlock detection

  Deadlock detection provides detailed information about deadlocks, including the roles of participants, the execution sequence of the deadlock, and the corresponding SQL statements. This helps you analyze the root cause of deadlocks and resolve them by analyzing and addressing cyclic dependencies in real time.

  

• Emergency response

  Based on the previously bound execution plans, OCP now provides emergency response capabilities for individual SQL statements and 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

  To facilitate data verification and migration for the new primary database, OCP supports starting the original primary database in read-only mode after a failover. After the original primary database is started in read-only mode, you can compare and correct data between the new primary database and the original primary database.

Alerts

OCP now supports custom alerts, allowing you to easily convert monitoring metrics into alert information.

Capacity management

The Resource Management page of a cluster now includes a replica view, enabling you to view the distribution of replicas from this perspective.

Backup and restore

OCP now supports tenant-level backups, allowing you to perform snapshot backups on tenants.

Feature enhancements

• Enhanced alerting capabilities: OCP now supports custom alert metrics, allowing you to easily convert monitoring metrics into alert information. Additionally, you can configure alerts for slow SQL statements.

• Enhanced organization management: You can now organize all resources under a single organization, making it easier to manage and identify resources.

• Enhanced cluster Performance Monitoring capabilities: The performance monitoring feature now includes statistics on block cache size, Cache Hit Rate, number of cache requests, and number of open cursors.

• Enhanced data middleware capabilities: OCP now collects logs from OBServer nodes and OBProxy components using ocp-agent 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 features.

Fixed issues

OCP V3.3.0 fixes the following issues:

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

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

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

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

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

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

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

• The issue where a large number of tmp log files are left in specific scenarios 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 on 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 a web browser. The following table lists the client requirements.

If you need to access OCP services on an iOS device, the following table lists the requirements.

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