OCP V4.0.2

#RNDate#2023-02-06

OCP V4.0.2 integrates the load balancing feature. This feature enables you to evenly distribute connections and automatically switch to a standby component in case of a failure.

Version information

• Version: V4.0.2

• Previous version: V4.0.1

• Version release date: February 6, 2023

• Supported upgrade path:

  • You can directly upgrade OCP V3.2.4 and later to the current version.

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

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

  Notice

  When you upgrade MetaDB V1479 to OCP V4.0.2, some table fields may fail to be upgraded. If you need to upgrade, we recommend that you contact Technical Support.

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 can be integrated with the load balancing products OBLB and SLB (available only in Apsara Stack) to support automatic configuration synchronization and updates.

• Clients (such as JDBC) can obtain OBProxy clusters and related configurations. The Applications dimension is supported for load balancing.

• AccessKey/SecretKey (AK/SK) management is supported. You can choose the AccessKey authentication method to call OCP API interfaces.

Feature enhancements

• OBProxy cluster management is optimized to avoid port inconsistencies among OBProxy nodes in the cluster.

• The following built-in alerts are added:

  • ocp_meta_db_disconnected: supports disconnection detection and alerts for OCP MetaDB and MonitorDB.

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

  • ocp_http_request_too_many_errors_occur: supports error detection and alerts for OCP API requests.

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

  • ob_server_stopped: supports service stop detection and alerts for OceanBase servers.

• The alert export feature is optimized. You can export the details of an alert rule and an alert template.

• You can add event-based alerts to an alert template.

• The system parameter ocp.alarm.event.resend-interval-seconds is added. The default value is 60 seconds. This parameter specifies the alert sending interval. A larger value reduces the alert sending frequency.

• The alert recovery strategy is optimized:

  • For threshold-based alerts, such as xxx_count > 1, the alert is automatically recovered only when the condition changes to xxx_count <= 1 and the duration exceeds the recovery cycle. If the monitoring data is lost, the alert is not automatically recovered.

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

• The alert detection logic is optimized:

  • Alert detection is optimized to reduce alert latency. The default detection cycle of an alert matches the data collection cycle. For a monitoring metric that is collected every 1 minute, the maximum alert latency is 70 s to 130 s. For a monitoring metric that is collected every 1 second, the maximum alert latency is 20 s.

  • You can adjust the alert detection cycle. A smaller detection cycle reduces alert latency. The theoretical alert latency is detection cycle + data collection cycle + 10 s (the offset for real-time monitoring). To avoid inaccurate real-time data, you can adjust the system parameter ocp.alarm.query.metric-offset-seconds.

• The backup logic is optimized. Before a backup is performed, the system checks whether the cluster is in the upgrading state to avoid backup failure.

• The backup and restore feature is optimized. A progress bar is added to Recovery Tasks.

• The display of diagnostic results is optimized. When the information scrolls, the key columns (such as the SQL text and diagnostic result) are fixed.

Fixed issues

OCP V4.0.2 fixes the following issues:

1. Fixed the issue where an OBServer node may fail to be added to an OceanBase cluster in some cases.

2. Fixed the issue where an error is displayed on the Overview page after a cluster is deleted.

3. Fixed the issue where the Too many rows are affected. SQL statement is not diagnosed in High-risk SQL of Diagnosis Center.

4. Fixed the issue where no data is displayed in End-to-end Diagnostics.

5. Fixed the issue where the storage usage of a cluster is incorrectly displayed in Diagnosis Center.

6. Fixed the issue where custom alerts are not triggered after OCP V3.x is upgraded to OCP V4.x.

7. Fixed the issue where the Host unavailable alert cannot be generated when the OCP agent process does not exist.

8. Optimized the display of some front-end information.

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 hardware requirements for the installation node.

Operating system requirements

The operating system requirements for installing OCP Server (including OCP-Agent) are as follows:

Client requirements

General users typically access OCP services through a web browser, so the client requirements are as follows:

If you need to access OCP services from an iOS device, the minimum operating system version is as follows:

For the best user experience, we recommend using a display with a resolution of 1440 x 810 or higher.