OCP V4.3.5

OCP V4.3.5 is officially released and is fully compatible with OceanBase Database V4.3.5. This version introduces a key feature, High Availability of the Arbitration Service, to ensure that OceanBase Database can continuously and stably provide services to the outside world. Additionally, this version supports OBKV-Redis instance monitoring capabilities. Moreover, this version includes over 20 improvements and optimizations in areas such as basic operation and maintenance, performance monitoring, inspection services, platform functionalities, significantly improving the usability of the product and enables users to manage the OceanBase Database more easily and efficiently.

Version information

• Current version: V4.3.5

• Previous version: V4.3.4 BP2

• Release date: March 3, 2025

• Supported upgrade paths:

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

  • To upgrade OCP V2.3.x and later but earlier than V3.2.4 to the current version, you need to upgrade OCP to V3.3.4 first.

  • If you use OCP of a version earlier than V2.3.0, you must upgrade OCP first to V2.3.x and then to V3.3.4.

Supported OceanBase Database versions

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

• OceanBase Database V4.x
• OceanBase Database V3.2.x
• OceanBase Database V3.1.x
• OceanBase Database V2.2.x
• OceanBase Database V2.1.x
• OceanBase Database V1.4.x

New Features

Basic Operation and Maintenance

• Arbitration Service:

  1. Supports high availability of arbitration services through arbitration service groups, ensuring that OceanBase Database can consistently and stably provide external services.
  2. Supports batch operations for arbitration service, such as replacing arbitration services, associating new clusters, and disassociating, thereby improving user operation efficiency.

• Cluster Management:

  1. Enables users to configuring automatic replica expansion when adding a zone, thereby improving user operation efficiency.
  2. Added cluster/OBServer startup time and online duration to facilitate users in observing database service capabilities (displaying startup time and online duration is not currently supported in cluster takeover scenarios).
  3. Supports displaying System_Memory / sys500 tenant size on Resource Management > Unit Distribution.
  4. Compaction Management now supports displaying the last three major compaction records (supported only in OceanBase V4.X).

• Tenant Management:

  1. Compaction Management now supports displaying the last three major compaction records (supported only in OceanBase V4.X).
  2. Supports creating database names and usernames with special characters (including - _). The character _ is a wildcard in MySQL, so please pay attention to the authorization scope to avoid authorization leakage.

Performance Monitoring

1. Enhanced Monitoring for OBKV-Redis Instances: Supports monitoring key performance indicators of OBKV-Redis instances, such as QPS and response time. (Limitations: OceanBase Database version ≥ 4.2.5 and in MySQL mode)
2. Monitoring Dashboard Enhancements: Supports importing and exporting monitoring indicator data in JSON format: Grafana/OCP, making it convenient for users to monitor the OceanBase database.
3. Added Support for OBProxy RPC Port Monitoring: odp_current_rpc_session/odp_rpc_request_total/odp_rpc_cost_total (Limitations: OBProxy version ≥ 4.3.0)

Inspection Services

Supports comparing parameters between different OBProxy instances within the same OBProxy cluster to avoid failures caused by parameter inconsistencies.

Backup and Recovery

1. Log backup tasks can be paused or resumed (supported only in OceanBase V4.X).
2. During data recovery, the system supports displaying a recovery window of up to 180 days (previously 7 days).
3. The Recovery Tasks module introduces a copy feature, allowing users to copy completed recovery tasks and modify certain parameters as needed. This will reduce repetitive work and significantly enhance the convenience and efficiency of operations.

Open API

1. Provides two Open APIs for starting and stopping OBProxy clusters.
2. Provides over 20 Open APIs for arbitration services/arbitration service groups.

Platform Functionalities

1. Operation and Maintenance Configuration: Supports visual configuration of the CPU and memory sizes used by the OCP Agent at both the cluster and host levels.
2. Software Package Management: Supports batch uploading of software packages, enhancing the convenience and efficiency of operations.
3. Log Service: Adapts to the log compression capability for observer.log (Limitations: OceanBase Database version: [4.2.3, 4.3.0) & [4.3.1, +∞).

Product Optimizations

Cluster Management

1. When deleting a cluster, the user is prompted to clean up all data and log backups under the cluster to prevent useless data from occupying storage space.
2. When creating a cluster with OceanBase version V4.X or above, the default setting for System_Memory / sys500 tenant size is 0 M, enabling the system to allocate the system_memory on demand.
3. In the scenario of primary and standby tenants, when upgrading the standby cluster, avoid allowing the standby tenant to be two or more database versions ahead of the primary tenant.

Tenant Management

1. When deleting a tenant, the user is prompted to clean up all data and log backups under the tenant to prevent useless data from occupying storage space.
2. Supports batch addition and modification of IPv4 addresses in the tenant whitelist, such as: 192.168.1.1-3, which indicates the three IP addresses: 192.168.1.1, 192.168.1.2, and 192.168.1.3 (only the last segment can be specified with a range).

OBProxy Management

1. Introduces the parameter template feature, providing two default parameter templates: one for version 4.2.1 and another for columnar storage replicas.
2. When creating a cluster, the version selection drop-down list is positioned before the password input field to prevent user misoperation in certain business scenarios.
3. Supports adding, displaying, and editing remarks on the load balancing page.

Others

• Host Management:

  Supports initializing hosts based on product type (OceanBase / OBProxy).

• Binlog Service:

  1. The Subscription Connection List for Binlog instances displays the real client IP address.
  2. Introduces the parameter template feature, providing five performance parameter templates: default, intermediate, advanced, super, and top-level.

• Performance Monitoring:

  1. When the user selects a monitoring duration greater than 3 days, the monitoring chart displays 1,440 monitoring points, enhancing the accuracy of trends and characteristics of monitoring data.
  2. Optimizes the time selection logic for performance monitoring to improve the convenience of query time setting operations.

• Alert Center:

  1. Adds monitoring metrics in the basic configuration of the Alert Rules interface, helping users troubleshoot based on these monitoring metrics.
  2. Supports adding labels when shielding alert objects.

Key Feature Interpretation

High Availability of the Arbitration Service

OceanBase V4.1 introduces the arbitration service, leveraging its significant advantage of low resource consumption and robust support for multi-cluster environments to create a more cost-effective high availability solution for the OceanBase database, such as the 2F1A/4F1A architecture. With this architecture, enterprises can effectively control resource costs while ensuring outstanding high availability for their database systems, significantly enhancing the cost-performance ratio.

However, it is essential to acknowledge the potential single point of failure in the arbitration service during operation. Once the arbitration service fails, the high availability of the OceanBase database cluster will inevitably degrade during the failure period, which may negatively impact business continuity and stability.

To effectively address this challenge, an arbitration service group has been introduced. In case an arbitration service node is abnormal and meets the replacement criteria, the system can switch the related clusters to other healthy nodes in the service group within seconds according to the priority setting, significantly improving the stability of OceanBase database clusters in complex environments and ensuring business continuity.

OceanBase V4.x Backup Strategy Optimization

• The cluster backup strategy serves as a means for batch operations on tenant backup strategies.
  • Creating a cluster-level backup strategy only takes effect for tenants that do not have a tenant-level backup strategy set.
  • When deleting a cluster backup strategy, the system will default to the cluster and tenant backup strategies and disable tenant-level log backup.
• Supports disabling log backup in both cluster and tenant backup strategies. The system will automatically enable log backup before data backup and disable log backup after data backup, primarily resolving the issue of excessively large log backups in certain business scenarios.
• The behavior of enabling/disabling log backup in cluster and tenant backup strategies takes the highest priority. Even if users manually enable or disable log backup, the system will enable or disable log backup according to the backup strategies by default.
• When cluster and tenant backup strategies are being edited, the system locks the storage configuration by default, meaning that changes to the storage path and the corresponding object storage AK/SK are not allowed. This is to avoid log archiving or data backup failures.
• When there is no cluster or tenant backup strategy, the system will record the status of log backup activation. If log backup is not enabled, then when the user manually initiates a backup, the system will automatically enable log backup before performing data backup. After the data backup is completed, the system will then disable log backup. If log backup is already enabled, it will remain enabled after the data backup is completed.

Bug fixes

The following issues are fixed in OCP V4.3.5:

• Fixed the issue with the retry logic for the OBProxy upgrade RPM task.
• Fixed the issue where OCP redirects to the xx.woff file by default after logging in.
• Fixed the issue where the compute_host_service was not updated to the latest version after the binlog upgrade.
• Fixed the issue where the alert detection failed in the case of negative clock offsets.
• Fixed the issue where resource permissions and object assignments for certain roles were incorrect in the scenario of the migration of custom roles.
• Optimized the number of metrics to reduce pressure on the agent and server sides, and disabled the collection of obkv-related metrics by default.
• Optimized the metrics about the response time at the 99th percentile by configuring separate metrics and SQL queries for each instance type.

Known issues

Limitations

Hardware requirements

OCP-Server can be installed on a physical server or in a Docker container. OCP-Server supports the multi-node HA deployment mode.

The following table lists the minimum hardware requirements of an OCP-Server node.

OCP-Agent takes up a few resources and has no special requirements for hardware.

Operating system requirements

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

Client requirements

Generally, users use browsers to access OCP. The following client requirements apply.

If you need to access OCP from an iOS device, the iOS version must meet the requirement listed in the following table.

We recommend that you use displays with a resolution greater than 1440 × 810 to ensure optimal use experience.