OCP V4.3.5

V4.3.5 BP7

Version information

• Version: V4.3.5 BP7

• Previous version: V4.3.5 BP6

• Version release date: January 5, 2026

Product behavior changes

• Fixed the issue where, in a single-node OCP cluster that manages more than 1,000 OBProxy nodes, the business connection is occasionally interrupted for less than one minute due to the failure to refresh the config server cache.
• Fixed the issue where, in OCP multi-cluster mode, after you create a primary-standby OceanBase cluster and execute the SwitchOver operation in the command-line interface, the cluster role in the mc_ob_cluster table is not automatically updated.
• Fixed the issue where, after you upgrade an OceanBase cluster, the import of the time zone table fails when you create a tenant.
• Fixed the issue where the ADMIN_VIEW role cannot access resources across organizations.

V4.3.5 BP6

Version information

• Version: V4.3.5 BP6

• Previous version: V4.3.5 BP5

• Version release date: November 4, 2025

Product behavior changes

• TopSQL query performance optimization strategy: When the SQL write pressure of MonitorDB exceeds the threshold, the system automatically initiates a downgrade mechanism to optimize the TopSQL record feature within a reasonable range. The core objective of this strategy is to prioritize the availability of the OAS query feature, which may result in the loss of some SQL records.
• Fixed the issue of Druid DataSource leakage under high load.
• Fixed the issue where indexes cannot be displayed for tables with quotes in the SQL diagnostic feature.
• Fixed the issue where the target organization is not fully displayed when sharing resources after searching for an organization on the organization list page.
• Fixed other known issues.

V4.3.5 BP5

Version information

• Version: V4.3.5 BP5

• Previous version: V4.3.5 BP4

• Version release date: August 29, 2025

Product behavior changes

Fixed some known issues.

V4.3.5 BP4

Version information

• Version: V4.3.5 BP4

• Previous version: V4.3.5 BP3

• Version release date: June 11, 2025

Product behavior changes

• Fixed the issue where the query for the tenant management list takes too long.
• Fixed the issue where an error is reported when the OCP Agent executes an O&M task and the Inactive Agent Modules step times out.
• Fixed the compatibility issue of the Open API for immediate backup.
• Fixed other known issues.

V4.3.5 BP3

Version information

• Version: V4.3.5 BP3

• Previous version: V4.3.5 BP2

• Version release date: April 17, 2025

Product behavior changes

Security issues are fixed, and the underlying framework and runtime environment for OCP are upgraded.

V4.3.5 BP2 Hotfix

Version information

• Version: V4.3.5 BP2 Hotfix

• Previous version: V4.3.5 BP2

• Version release date: June 11, 2025

Product behavior changes

• Fixed the issue where the tenant management list query takes too long.
• Fixed the issue where an error is reported when the OCP Agent executes an O&M task and the Inactive Agent Modules step times out.
• Fixed the compatibility issue of the Open API for immediate backup.
• Fixed other known issues.

V4.3.5 BP2

Version information

• Version: V4.3.5 BP2

• Previous version: V4.3.5 BP1

• Version release date: March 27, 2025

Product behavior changes

Supports OceanBase Database Standalone Edition: standalone installation package (experimental feature).

V4.3.5 BP1

Version information

• Version: V4.3.5 BP1

• Previous version: V4.3.5

• Version release date: March 20, 2025

Product behavior changes

• Fixed the logic error in retrying the OBProxy upgrade RPM task.
• Fixed the issue where OCP redirects to the xx.woff file by default after login.
• Fixed the issue where the compute_host_service is not updated to the latest version after the Binlog cluster upgrade.
• Fixed the issue where the alert detection fails when the clock offset is negative.
• Fixed the issue where resource permissions and object allocations for some custom roles are incorrect during role migration.
• Optimized the number of metrics to reduce the pressure on the Agent and Server ends. By default, the collection of OBKV-related metrics is disabled.
• Optimized the P99 raw metrics. Separate metrics and query SQL statements are configured for each instance type.

V4.3.5

OCP V4.3.5 is officially released and is fully compatible with OceanBase Database V4.3.5. This version introduces the key feature of high availability for arbitration services, ensuring continuous and stable service provision by OceanBase Database. Additionally, this version supports monitoring capabilities for OBKV-Redis and includes over 20 improvements and optimizations in areas such as basic O&M, performance monitoring, inspection services, and platform features. These enhancements significantly improve the usability of the product, enabling users to more easily and efficiently manage OceanBase Database.

Version information

• Version: V4.3.5

• Previous version: V4.3.4 BP2

• Version release date: March 4, 2025

• Supported upgrade path:

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

  • If you use OCP V2.3.x or later but earlier than V3.2.4, you must first upgrade to OCP V3.3.4.

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

Supported OceanBase Database versions

OCP V4.3.5 supports the following OceanBase Database versions:

• OceanBase V2.2.76 and OceanBase V2.2.77

• OceanBase V3.1.x

• OceanBase V3.2.x

• OceanBase V4.0.x

• OceanBase V4.1.x

• OceanBase V4.2.x

• OceanBase V4.3.x

New features

Basic O&M

• Arbitration Service:

  • You can use an arbitration service group to implement high availability of the arbitration service. This ensures that OceanBase Database continues to provide services.
  • You can perform batch operations on the arbitration service, such as replacing the arbitration service, associating a new cluster, or disassociating a cluster. This improves user efficiency.

• Cluster management:

  • You can configure automatic replica expansion for tenants in a zone. This improves user efficiency.
  • The Start Time and Online Duration of a cluster and an OBServer node are displayed. This helps you observe the database service capability. In takeover scenarios, the Start time and Online duration are not displayed.
  • The Unit Distribution page of Resource Management displays the size of System_Memory / 500.
  • If OceanBase Database is of V4.X, the Compaction Management page displays the last three merge records.

• Tenant Management:

  • You can create databases and users with the special characters - and _. Note that _ is a wildcard in MySQL. Make sure to specify the authorization scope to avoid authorization leakage.
  • If OceanBase Database is of V4.X, the Compaction Management page displays the last three merge records.

Performance monitoring

• If OceanBase Database is of V4.2.5 or later and the tenant is in MySQL mode, you can monitor the OBKV-Redis instance. The monitoring metrics include QPS and Response Time.
• You can import and export Grafana/OCP monitoring metrics in JSON format on the dashboard. This helps you monitor OceanBase Database.
• If OBProxy is of V4.3.0 or later, you can monitor the OBProxy RPC port. The monitoring metrics include RPC session count, RPC request count, and RPC request latency.

Inspection service

You can compare parameters of different OBProxies in the same OBProxy cluster. This avoids production faults caused by parameter inconsistency.

Backup and restore

• If OceanBase Database is of V4.X, you can pause or resume a log backup task.
• During data restore, the system displays the restore interval for the last 180 days instead of the last 7 days.
• The restore task module supports the copy feature. You can copy a completed restore task and modify some parameters as needed. This reduces repetitive work and improves the convenience and efficiency of operations.

Open API

• Two Open APIs are provided: one for starting an OBProxy node and the other for stopping an OBProxy node.
• Twenty plus Open APIs are provided for arbitration services and service groups.

Platform features

• O&M Configuration: You can visually configure the CPU and memory size used by the OCP Agent for a cluster or a host.
• Software Package Management: You can upload software packages in batches. This improves the convenience and efficiency of operations.
• Log Service: If OceanBase Database is of V4.2.3 but not V4.3.0, the observer.log compression feature is supported.

Product optimization

Cluster management

• When you delete a cluster, a prompt appears to clear all data and log backups in the cluster, to prevent unnecessary data from occupying storage space.
• When you create an OceanBase V4.X or later cluster, the default value of the system_memory/500 tenant is 0Mib, to enable the system to allocate system_memory memory as needed.
• In a primary-standby tenant scenario, when you upgrade a standby cluster, the standby tenant does not have a database version that is two or more versions higher than that of the primary tenant.

Tenant management

• When you delete a tenant, a prompt appears to clear all data and log backups in the tenant, to prevent unnecessary data from occupying storage space.
• You can add or modify IPv4 addresses in a tenant's allowlist in batches. For example, xxx.xxx.xxx.1-3 indicates the IP addresses xxx.xxx.xxx.1, xxx.xxx.xxx.2, and xxx.xxx.xxx.3. Only the last segment can be filled with a range.

OBProxy management

• The parameter template feature is added. Two default parameter templates are provided: 4.2.1 Default Parameter Template and Default Parameter Template for Columnar Replicas.
• When you create an OBProxy cluster, the version selection is placed before you enter the root@proxysys password, to prevent users from making mistakes in some business scenarios.
• The Load Balancing page supports adding, displaying, and editing remarks.

Others

• Host Management: You can initialize a host based on its type (OceanBase or OBProxy).

• Binlog Service:

  • Binlog Instance > Subscription Connection List displays the real client IP address.
  • The parameter template feature is added. Five default performance parameter templates are provided: Default Performance Parameter Template, Intermediate Performance Parameter Template, Advanced Performance Parameter Template, Superior Performance Parameter Template, and Ultimate Performance Parameter Template.

• Performance Monitoring:

  • When the monitoring time is greater than 3 days, the monitoring chart displays 1440 monitoring points to improve the accuracy of the monitoring data's trend and characteristics.
  • The selection logic of Custom Time in Performance Monitoring is optimized to improve the convenience of setting the query time.

• Alert Center:

  • Alert Rules > Basic Settings supports adding monitoring metrics to facilitate troubleshooting based on the monitoring metrics.
  • When you shield an alert object, you can shield a specified metric by using Tag.

Key features

High availability of arbitration service

OceanBase Database V4.1 provides arbitration service. The arbitration service is characterized by low resource consumption and strong support for multiple clusters. It successfully creates a more cost-effective high availability solution for OceanBase Database, such as the 2F1A or 4F1A architecture. This architecture allows enterprises to effectively control resource costs while ensuring excellent high availability of the database system, greatly improving the cost-effectiveness of the system. However, it is important to note that the arbitration service has a single point of failure. If the arbitration service fails, the high availability of the OceanBase cluster will degrade during the failure period, which may negatively impact the continuity and stability of the business. To address this challenge, the system builds an arbitration service group. When an arbitration service node in the group fails and meets the replacement conditions, the system can quickly switch the relevant cluster to another healthy arbitration service node within seconds. This ensures the stable operation of the OceanBase cluster under various complex conditions and prevents any impact on the business.

Usage notes:

• The versions of arbitration services in the same arbitration service group must be consistent.
• An arbitration service group must contain at least two arbitration service addresses.
• After an arbitration service group switches to another arbitration service node, you must reconfigure the association between the cluster and the arbitration service group based on the actual business situation to avoid overloading of the arbitration service.
• Arbitration service group and plan: When the OBServer process of an arbitration service exits abnormally and is restarted, there is no functional conflict. That is, when an arbitration service fails, it can be automatically restarted by a plan, and it will also be replaced if it meets the replacement conditions of the arbitration service group.
• You can create, upgrade, edit, and delete an arbitration service group.

Optimization of backup strategies for OceanBase Database 4.x

• Cluster backup strategy supports batch operations on tenant backup strategies:

  • A cluster-level backup strategy takes effect only for tenants that do not have a tenant-level backup strategy.
  • When you delete a cluster backup strategy, the system deletes the cluster and tenant backup strategies by default and disables tenant-level log backup.

• You can disable log backup in a cluster or tenant backup strategy. By default, the system enables log backup before data backup and disables log backup after data backup. This mainly solves the problem of excessive log backup in some business scenarios.

• The enable/disable log backup behavior in a cluster or tenant backup strategy has the highest priority. Even if you manually disable or enable log backup, the system will enable or disable log backup based on the backup strategy.

• When you edit a cluster or tenant backup strategy, the storage configuration is grayed out by default. That is, you cannot change the storage path or the AccessKey and SecretKey of the corresponding object storage service. This prevents log archiving or data backup from failing.

• If no cluster or tenant backup strategy exists, the system records the log backup enable status. If log backup is not enabled, the system enables log backup before data backup and disables log backup after data backup when you manually initiate a backup. If log backup is already enabled, it remains enabled after data backup.

Fixed issues

OCP V4.3.5 fixes the following issues:

• Fixed the issue where the cluster list cannot be displayed when the cluster is unavailable.
• Fixed the issue where a false alert is triggered when the location cache fails.
• Fixed the issue where the data size is incorrectly displayed in the table data statistics.

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 following table lists the minimum hardware requirements for OCP-Server nodes.

OCP-Agent consumes very few resources and has no special requirements for the hardware resources of 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 usually access OCP services through a web browser. The following table lists the requirements for the client.

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

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