OCP V4.3.5

V4.3.5 BP4

Version information

• Version number: V4.3.5 BP4

• Previous version: V4.3.5 BP3

• Version release date: June 11, 2025

Feature updates

• Fixed the issue where the query in the tenant management list takes an excessively long time.
• Fixed the issue where an error is returned when the OCP Agent is in the Inactive Agent Modules step during the execution of an O&M task.
• Fixed the compatibility issue with the immediate backup Open API.
• Fixed some other known issues.

V4.3.5 BP3

Version information

• Version number: V4.3.5 BP3

• Previous version: V4.3.5 BP2

• Version release date: April 17, 2025

Product behavior changes

The underlying framework, runtime environment, and other components used for OCP have been upgraded, and security issues have been fixed.

V4.3.5 BP2 Hotfix

Version information

• Version number: V4.3.5 BP2 Hotfix

• Previous version: V4.3.5 BP2

• Version release date: June 11, 2025

Feature updates

• Fixed the issue where the query in the tenant management list takes an excessively long time.
• Fixed the issue where an error is returned when the OCP Agent is not active during the Inactive Agent Modules step of an O&M task.
• Fixed the compatibility issue with the immediate backup Open API.
• Fixed some other known issues.

V4.3.5 BP2

Version information

• Version number: V4.3.5 BP2

• Previous version: V4.3.5 BP1

• Version release date: March 27, 2025

Feature updates

Adaptation for standalone installation package of OceanBase Database (Experimental).

V4.3.5 BP1

Version information

• Version number: V4.3.5 BP1

• Previous version: V4.3.5

• Version release date: March 20, 2025

Feature updates

• The retry logic for upgrading OBProxy RPM was fixed.
• After logging in to OCP, the default redirection to the xx.woff file was fixed.
• The issue where compute_host_service did not update to the latest version after upgrading the Binlog cluster was fixed.
• The problem where alert detection failed when the clock offset was negative was fixed.
• The issue where resource permissions and object allocations of some custom roles were incorrect during migration was fixed.
• The number of metrics was optimized to reduce the pressure on both the Agent and Server. By default, the collection of OBKV-related metrics is disabled.
• The original P99 metrics were optimized by configuring separate metrics and query SQL for each instance type.

V4.3.5

OCP V4.3.5 is now available, offering full compatibility with OceanBase Database V4.3.5. This version introduces a critical feature - high availability of arbitration service - to ensure the continuous and stable service of OceanBase Database. Additionally, this version supports monitoring for OBKV-Redis, and includes over 20 enhancements and optimizations in basic O&M, performance monitoring, inspection services, and platform features, significantly improving the ease of use of the product and enabling users to manage OceanBase Database more conveniently and efficiently.

Version information

• Version number: V4.3.5

• Previous version: V4.3.4 BP2

• Version release date: March 4, 2025

• Supported upgrade path

  • Directly upgrade OCP V3.2.4 and later to this version.

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

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

Supported OceanBase Database versions

OCP V4.3.5 supports the OceanBase Database versions listed in the following table.

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

New features

Basic O&M

• Arbitration Service:

  • Supports high availability of arbitration service through arbitration service groups to ensure the continuous and stable service of OceanBase Database.
  • Supports batch operations on arbitration services including replacement, association with new clusters, and disassociation, to improve user efficiency.

• Cluster Management:

  • Supports configuring tenant auto-scaling replicas in new zones to enhance user efficiency.
  • Adds Start Time and Online Duration information for clusters and OBServer nodes to facilitate monitoring of database capabilities. These fields are temporarily unavailable in cluster takeover scenarios.
  • Supports displaying the size of System_Memory / 500 Tenants in Resource Management > Unit Distribution.
  • For OceanBase Database V4.X, Compaction Management supports displaying the three most recent compaction records.

• Tenant Management:

  • Supports creating databases and users with names containing the special characters - and _. Note that the character _ is a MySQL wildcard. Exercise caution when granting privileges to avoid privilege leakage.
  • For OceanBase Database V4.X, Compaction Management supports displaying the three most recent compaction records.

Performance Monitoring

• For OceanBase Database V4.2.5 and above with MySQL tenants, adds monitoring capabilities for OBKV-Redis instances, including QPS and Response Time.
• Supports importing and exporting monitoring metrics in JSON format between Grafana and OCP to facilitate OceanBase Database monitoring.
• For OBProxy V4.3.0 and above, adds monitoring capabilities for OBProxy RPC ports, including RPC Sessions, RPC Requests, and RPC Request Duration.

Inspection Service

Supports comparing parameters of different OBProxy instances within the same OBProxy cluster to prevent production failures due to parameter discrepancies.

Backup and Restore

• For OceanBase Database V4.X, supports pausing and resuming log backup tasks.
• Extends the displayable restore period from 7 to 180 days.
• Adds the ability to copy completed restore tasks with modifiable parameters, reducing repetitive work and significantly enhancing convenience and efficiency.

Open API

• Opens 2 APIs for starting and stopping OBProxy.
• Opens over 20 APIs for arbitration services and service groups.

Platform features

• O&M Configuration: Allows you to configure the CPU and memory resources for the OCP Agent in the console on the cluster or host level.
• Software Package Management: Supports batch uploading of software packages to improve convenience and efficiency.
• Log Service: Adapts to the observer.log compression feature of OceanBase Database V4.2.3 and later (excluding V4.3.0).

Product optimization

Cluster management

• When a user deletes a cluster, a prompt appears to ask the user to clear all data and log backups in this cluster to avoid the occupation of storage space by useless data.
• When you create an OceanBase cluster of V4.0 or later, the system_memory/500 tenant is set to 0 MiB by default, so that the system can allocate memory in system_memory on demand.
• In the primary-standby tenant mode, when you upgrade the standby cluster, the database version of the standby tenant cannot be more than two versions ahead of that of the primary tenant.

Tenant management

• When a user deletes a tenant, a prompt appears to ask the user to clear all data and log backups in this tenant to avoid the occupation of storage space by useless data.
• You can add or modify IPv4 addresses in the tenant allowlist in batches. For example, xxx.xxx.xxx.1-3 indicates xxx.xxx.xxx.1, xxx.xxx.xxx.2, and xxx.xxx.xxx.3. Only the last segment of the IP address can contain a range.

OBProxy management

• The parameter template feature is provided. Two default parameter templates are provided: 4.2.1 Default Parameter Template and Replica Parameter Template.
• The version selection is placed before the input of root@proxysys password when you create an OBProxy cluster, to prevent user misoperation in some business scenarios.
• The Remarks tab is added on the Load Balancing page, which supports adding, displaying, and editing remarks.

Others

• Host management: You can initialize hosts by product type (OceanBase or OBProxy).

• Binlog Service:

  • In the Binlog Instance > Subscription Connection List list, the IP address of the actual client is displayed.
  • The parameter template feature is provided. Five default performance parameter templates are provided: Default Performance Parameter Template, Medium Performance Parameter Template, High Performance Parameter Template, Super High Performance Parameter Template, and Ultra High Performance Parameter Template.

• Performance Monitoring:

  • When the monitoring period is more than three days, 1,440 monitoring points are displayed on the monitoring chart to improve the accuracy of monitoring data trends and features.
  • The selection logic of Performance Monitoring > Custom Time is optimized to improve the convenience of query time setting.

• Alert Center:

  • In the Alert Rules > Basic Settings tab, monitoring metrics are added for easy troubleshooting.
  • You can shield monitoring metrics for specified indicators in the alarmed object.

Key feature insights

High availability of arbitration service

OceanBase Database V4.1 introduces arbitration capabilities, leveraging its low resource consumption and strong support for multiple clusters to offer a cost-effective high availability solution for OceanBase Database, such as the 2F1A/4F1A architecture. This architecture allows enterprises to maintain high availability of the database system while effectively controlling resource costs, significantly enhancing the cost-effectiveness of the system. However, it is important to note that the arbitration service is vulnerable to single point of failure. If the arbitration service fails, the high availability of the OceanBase cluster will inevitably degrade during the failure period, potentially impacting business continuity and stability. To address this challenge, the system allows for the creation of arbitration service groups, enabling fast switchover of clusters to healthy arbitration service nodes in seconds upon an exception in an arbitration service node that meets the replacement conditions. This ensures stable operation of OceanBase clusters in various complex scenarios, ensuring business continuity.

Considerations:

• All arbitration services in the same group must be of the same version.
• We recommend that each arbitration service group contain at least 2 arbitration service endpoints.
• After arbitration service switchover in a group is completed, make sure to reconfigure the cluster and arbitration service association based on your actual business needs to prevent any arbitration service from becoming overloaded.
• Arbitration service group and plan: There is no functional conflict between an arbitration service group and a plan. If an arbitration service in a plan fails, it can be automatically restarted by the plan. It can also be replaced by an arbitration service in the group if it meets the replacement conditions.
• The feature supports four main functions: creating, upgrading, editing, and deleting an arbitration service group.

Optimization of backup strategies in OceanBase Database 4.x

• Cluster backup strategies, which allow for batch operations on tenant backup strategies:

  • A cluster backup strategy created only takes effect when no tenant-level backup strategy is set.
  • When deleting a cluster backup strategy, the system will default to deleting the corresponding tenant backup strategy and disabling tenant-level log backup.

• The feature now supports disabling log backup in both cluster and tenant backup strategies. The system will default to enabling log backup before data backup and disabling it after data backup, primarily to address the issue of excessive log backup in some business scenarios.

• The enabling or disabling of log backup in cluster or tenant backup strategies has the highest priority. If users manually disable or enable log backup, the system will default to following the backup strategy to enable or disable log backup.

• When editing cluster or tenant backup strategies, the storage configuration is default to be grayed out, meaning users cannot change the storage path or corresponding object storage AK/SK, to prevent failures in log archiving or data backup.

• If no cluster or tenant backup strategy is available, the system will record the log backup status. If log backup is not enabled, the system will default to enabling log backup before data backup and disabling it after data backup when users manually initiate a backup. If log backup is enabled, it will remain enabled after data backup.

Bug fixes

OCP V4.3.5 fixes the following bugs:

• Fixed the issue where the cluster list cannot be displayed when the cluster is unavailable.
• Fixed the issue of false alarms in Location Cache failures.
• Fixed the issue where the data size is displayed incorrectly in table data statistics.

Known issues

Limitations on versions

Hardware requirements

OCP-Server can be installed on a physical server or in a Docker container. OCP-Server supports multi-node and high-availability deployments.

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

OCP-Agent occupies few resources and has no special hardware requirements.

Operating system requirements

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

Client requirements

Generally, users access OCP services through browsers. The following client requirements apply.

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

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