OCP V4.0.2

#RNDate#2023-02-06

OCP V4.0.2 integrates the load balancing feature, enabling businesses to better utilize the capabilities of OceanBase Database distributed clusters and achieve balanced connection distribution and automatic failover.

Version information

• Version: V4.0.2

• Previous version: V4.0.1

• Version release date: February 6, 2023

• Supported upgrade path:

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

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

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

  Notice

  MetaDB V1.4.79 is a version of OCP. When you upgrade MetaDB V1.4.79 to OCP V4.0.2, some table fields may fail to be upgraded. If you need to upgrade MetaDB V1.4.79, we recommend that you contact Technical Support.

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

• Clients (such as JDBC) can obtain OBProxy clusters and related configurations to implement load balancing capabilities based on Applications.

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

Feature enhancements

• OBProxy cluster management is optimized to avoid the problem of inconsistent ports on OBProxy nodes in the cluster.

• The following built-in alert items are added:

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

  • ocp_http_request_timeout: supports detection and alerts for OCP interface request timeouts.

  • ocp_http_request_too_many_errors_occur: supports detection and alerts for OCP interface request errors.

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

  • ob_server_stopped: supports detection and alerts for OceanBase server service stoppage.

• The alert export feature is optimized. Alert rules support exporting details, and alert templates can also be exported.

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

• The system parameter ocp.alarm.event.resend-interval-seconds is added. This parameter adjusts the alert sending interval. By default, an alert is sent every 1 minute. Increasing this parameter reduces the alert sending frequency.

• The alert recovery strategy is optimized:

  • For threshold-based alerts (e.g., xxx_count > 1), the alert is automatically recovered only when xxx_count <= 1 is detected and the duration exceeds the recovery cycle. If the monitoring data is lost, the alert will not be 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 alert detection cycle matches the data collection cycle. For monitoring data collected every 1 minute, the maximum alert latency is approximately 70 to 130 seconds. For monitoring data collected every 1 second, the maximum alert latency is approximately 20 seconds.

  • Users can adjust the alert detection cycle. A shorter cycle results in lower alert latency. The theoretical alert latency is detection cycle + data collection cycle + 10 seconds (the offset for real-time monitoring. To avoid inaccurate real-time data, you can adjust this offset using 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 an upgrade state to avoid backup failures.

• The backup and restore feature is optimized. Data backup tasks and Recovery Tasks now display progress bars.

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

Fixed issues

OCP V4.0.2 fixes the following issues:

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

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

3. Fixed the issue where Too many rows are affected. SQL statements are not diagnosed in High-risk SQL statements.

4. Fixed the issue where no data is found in End-to-end diagnostics.

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

6. Fixed the issue where custom alerts cannot be triggered after upgrading from OCP V3.x 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 several issues where front-end information is not fully displayed.

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 shown in the following table.

OCP-Agent consumes very few resources and does not have special requirements for the hardware resources of the installation node.

Operating system requirements

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

Client requirements

General users access OCP services through a web browser. The following table shows the client requirements.

If you want to access OCP services on an iOS device, the minimum version is shown in the following table.

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