OCP V4.0.2

OCP V4.0.2 integrates with load balancing products, enabling businesses to better leverage the distributed cluster capabilities of OceanBase Database for connection balancing and automatic failover.

Version information

• Version: V4.0.2

• Previous version: V4.0.1

• Release date: February 06, 2023

• Supported upgrade path:

  • Currently, only upgrades from OCP V3.2.4 and later versions are supported.

  • For OCP V2.3.x and later, but earlier than V3.2.4, you must first upgrade to OCP V3.3.4.

  • For OCP versions earlier than V2.3.0, you must first upgrade to OCP V2.3.x, then to OCP V3.3.4.

  Notice

  For OCP with MetaDB version 1479, some table fields may not be upgradable when upgrading to V4.0.2. If you need to upgrade, it is recommended to contact technical support first.

Supported OceanBase Database versions

OCP V4.0.2 supports the following versions of OceanBase Database:

• OceanBase V1.4.x

• OceanBase V2.1.x

• OceanBase V2.2.x

• OceanBase V3.1.x

• OceanBase V3.2.x

• OceanBase V4.x

New features

• OBProxy clusters now support integration with load balancing products OBLB and SLB (Alibaba Cloud Apsara Stack only), enabling automatic configuration synchronization and updates.

• Supports clients (such as JDBC) to obtain OBProxy clusters and related configurations, implementing load balancing capabilities at the application level.

• Implemented AK/SK management. Users can choose to call OCP APIs through AccessKey authentication.

Feature enhancements

• Optimized OBProxy cluster management to avoid inconsistencies in OBProxy node ports within a cluster.

• Added built-in alert items:

  • ocp_meta_db_disconnected: Supports detection and alerting for disconnections to OCP's MetaDB or MonitorDB.

  • ocp_http_request_timeout: Supports detection and alerting for timeouts in OCP interface requests.

  • ocp_http_request_too_many_errors_occur: Supports detection and alerting for errors in OCP interface requests.

  • ocp_alarm_detect_timeout: Supports detection and alerting for timeouts in OCP alert rule detection.

  • ob_server_stopped: Supports detection and alerting for OceanBase servers stopping service.

• Optimized the alert export feature. Alert rules now support exporting detail fields, and alert templates are also supported for export.

• Supports adding event-based alerts to alert templates.

• Added the system parameter ocp.alarm.event.resend-interval-seconds to adjust the alert sending interval. By default, an alert is generated every minute. Increasing this parameter reduces the alert sending frequency.

• Optimized alert recovery strategies:

  • Threshold-based alerts: For example, alerts like xxx_count > 1. An alert will automatically recover only when xxx_count <=1 is detected for more than its recovery period. If monitoring is lost, the alert will not automatically recover.

  • Non-threshold-based alerts: Their recovery still follows the recovery period.

• Optimized alert detection logic:

  • Optimized alert detection to reduce alert latency. The default detection cycle for alerts matches its data collection cycle. For monitoring collected every 1 minute, the maximum alert latency is about 70 s to 130 s; for monitoring collected every 1 second, the maximum alert latency is about 20 s.

  • Supports users to independently adjust the alert detection cycle. A smaller cycle results in lower alert latency. The theoretical latency is detection cycle + data collection cycle + 10 s (the offset for real-time monitoring. To avoid inaccuracies in real-time data, it can be adjusted using the system parameter ocp.alarm.query.metric-offset-seconds).

• Optimized backup logic. Checks whether the cluster is in an upgrade state before backup to avoid backup failures.

• Optimized the backup and restore functions. Added progress bars for data backup tasks and restore tasks.

• Optimized diagnostic result display. Fixed key information columns (SQL text, diagnostic results) when information scrolls.

Fixed issues

OCP V4.0.2 fixes the following issues:

1. Fixed an issue where adding an OBServer node to an OceanBase cluster might fail in certain situations.

2. Fixed an issue where, after deleting a cluster and entering the Overview page, an error message would appear on the page.

3. Fixed the issue where Too many rows are affected. SQL statements were not diagnosed in Diagnostic Center > High-Risk SQL.

4. Fixed the issue where data could not be found in End-to-End Diagnostics.

5. Fixed the issue where the frontend display of cluster storage usage was incorrect in Diagnostic Center.

6. Fixed the issue where custom alerts could not be triggered after upgrading from OCP V3.x to OCP V4.x.

7. Fixed the issue where a Host Unavailable alert could not be generated when the OCP agent process did not exist.

8. Optimized several frontend information display issues that were incomplete.

Known Issues

Version Usage Restrictions

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.

OCP-Agent consumes very few resources and has no specific hardware requirement 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, so the client requirements are as follows.

If you need to access OCP from a device with 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 x 810.