OCP V4.0.2

OCP V4.0.2 integrates the load balancing feature. This feature allows you to better leverage the capabilities of OceanBase Database distributed clusters to achieve even distribution of connections and automatic failover.

Version information

• Version: V4.0.2

• Previous version: V4.0.1

• Version release date: February 6, 2023

• Supported upgrade path:

  • Only direct upgrades from OCP V3.2.4 and later are supported.

  • For OCP V2.3.x and later, but before 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

  When upgrading MetaDB from version 1479 to V4.0.2, some table fields may not be upgraded. If you have upgrade needs, we recommend that you contact technical support first.

Supported OceanBase Database versions

OCP V4.0.2 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

• OceanBase V4.x

New features

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

• Clients (such as JDBC) can now retrieve OBProxy cluster and related configuration details, allowing for load balancing capabilities based on the Applications dimension.

• AK/SK management is now supported, allowing users to choose AccessKey-based authentication for calling OCP API interfaces.

Feature enhancements

• OBProxy cluster management has been optimized to prevent port inconsistencies among OBProxy nodes within the cluster.

• New built-in alert items have been added:

  • ocp_meta_db_disconnected: Supports detection and alerts for disconnections in OCP's MetaDB and MonitorDB.

  • ocp_http_request_timeout: Supports detection and alerts for timeout in OCP API requests.

  • ocp_http_request_too_many_errors_occur: Supports detection and alerts for errors in OCP API requests.

  • ocp_alarm_detect_timeout: Supports detection and alerts for timeout in OCP alert rule detection.

  • ob_server_stopped: Supports detection and alerts for the stopping of OceanBase servers.

• Alert export functionality has been enhanced, allowing for the export of detailed fields and alert templates.

• Event-based alerts can now be added to alert templates.

• A new system parameter, ocp.alarm.event.resend-interval-seconds, has been introduced to adjust the alert sending interval. By default, an alert is sent every minute. Increasing this parameter can reduce the alert sending frequency.

• Alert recovery strategies have been optimized:

  • For threshold-based alerts (e.g., xxx_count > 1), alerts will automatically recover only when xxx_count <= 1 is detected and the duration exceeds the recovery cycle. If the monitoring data is lost, the alert will not automatically recover.

  • For non-threshold-based alerts, recovery still follows the recovery cycle.

• Alert detection logic has been optimized:

  • Alert detection has been improved to reduce alert latency. The default detection cycle matches the data collection cycle. For monitoring data collected every minute, the maximum alert latency ranges from 70 to 130 seconds. For monitoring data collected every second, the maximum alert latency is approximately 20 seconds.

  • Users can now adjust the alert detection cycle. A shorter cycle results in lower alert latency, theoretically as low as detection cycle + data collection cycle + 10 seconds (the offset for real-time monitoring, which can be adjusted using the system parameter ocp.alarm.query.metric-offset-seconds to avoid inaccuracies in real-time data).

• Backup logic has been optimized to check if the cluster is in an upgrade state before initiating a backup, preventing backup failures.

• Backup and restore functionality has been enhanced with progress bars for Data Backup Tasks and Recovery Tasks.

• Diagnostic results display has been optimized, with key columns (SQL text, diagnostic results) fixed during information scrolling.

Fixed issues

OCP V4.0.2 fixes the following issues:

1. Fixed an issue where adding an OBServer node to an OceanBase cluster could fail under certain conditions.

2. Fixed an issue where, after deleting a cluster, entering the Overview page would result in an error message.

3. Fixed an issue where the Too many rows are affected. SQL diagnostic item was not being detected in the High-Risk SQL section of the Diagnostic Center.

4. Fixed an issue where no data was found in the End-to-End Diagnosis section.

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

6. Fixed an issue where custom alerts were not triggered after upgrading from OCP V3.x to OCP V4.x.

7. Fixed an issue where the Host Unavailable alert could not be generated when the OCP agent process was missing.

8. Optimized several frontend display issues where information was incomplete.

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 little resources and has no special hardware requirements for the installation node.

Operating system requirements

The following table lists the operating system requirements for installing OCP-Server (including OCP-Agent).

Client requirements

General users access OCP services through a web browser, so the following client requirements apply.

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

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