OCP V4.3.5

V4.3.5 BP7

Version information

• Version: V4.3.5 BP7

• Previous version: V4.3.5 BP6

• Release date: January 5, 2026

Product behavior changes

• Fixed the issue where refreshing the config server cache failed in single-node OCP managing over 1,000 OBProxy nodes, causing occasional business disconnections (lasting less than 1 minute).
• Fixed the issue where the cluster role was not automatically updated in the mc_ob_cluster table after creating primary/standby OceanBase clusters in multi-cluster mode of OCP and executing SwitchOver via the command line.
• Fixed the issue where importing the timezone table failed during tenant creation after upgrading an OceanBase cluster.
• Fixed the issue where the ADMIN_VIEWER role could not access resources across organizations.

V4.3.5 BP6

Version information

• Version: V4.3.5 BP6

• Previous version: V4.3.5 BP5

• Release date: November 4, 2025

Product behavior changes

• TopSQL query performance optimization strategy: When the SQL write pressure on MonitorDB exceeds the threshold, the system automatically activates a degradation mechanism to optimize and adjust the TopSQL recording feature within a reasonable range. The core objective of this strategy is to prioritize ensuring the availability of the OAS query feature. The impact may be the loss of some SQL records.
• Fixed an issue where Druid DataSource leaks occur under heavy load.
• Fixed an issue where the SQL diagnostics feature fails to display indexes for tables with quotes.
• Fixed an issue where, after searching for an organization on the organization list page, the target organization is not fully displayed when sharing resource configurations.
• Fixed other known issues.

V4.3.5 BP5

Version information

• Version: V4.3.5 BP5

• Previous version: V4.3.5 BP4

• 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

• Release date: June 11, 2025

Product behavior changes

The underlying framework and runtime environment used by OCP have been upgraded, and some known issues have been fixed.

V4.3.5 BP3

Version information

• Version: V4.3.5 BP3

• Previous version: V4.3.5 BP2

• Release date: April 17, 2025

Product behavior changes

Fixed identified security issues and upgraded the foundational frameworks and runtime environments used by OCP.

V4.3.5 BP2

Version information

• Version: V4.3.5 BP2

• Previous version: V4.3.5 BP1

• Release date: March 27, 2025

Product behavior changes

Adapted for 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

• Release date: March 20, 2025

Product behavior changes

• Fixed an issue where the retry logic for the OBProxy upgrade RPM task was incorrect.
• Fixed an issue where logging into OCP would redirect to a xx.woff file by default.
• Fixed an issue where compute_host_service was not updated to the latest version after a Binlog cluster upgrade.
• Fixed an issue where negative clock skew caused alert detection failure.
• Fixed an issue where resource permissions and object allocation were incorrect for some roles during custom role migration.
• Optimized the number of metrics to reduce pressure on both the Agent and Server sides. By default, OBKV-related metric collection is disabled.
• Optimized the P99 raw metric by configuring separate metrics and query SQLs for each instance type.

V4.3.5

OCP V4.3.5 is officially released, fully compatible with OceanBase Database V4.3.5. This version introduces a key feature: high availability for the arbitration service, ensuring continuous and stable service delivery from OceanBase. It also supports OBKV-Redis monitoring capabilities and includes over 20 improvements and optimizations in basic operations, performance monitoring, inspection services, and platform functionality, effectively enhancing product usability and helping users manage OceanBase databases more conveniently and efficiently.

Version information

• Version: V4.3.5

• Previous version: V4.3.4 BP2

• Release date: March 4, 2025

• Supported upgrade path:

  • Currently, only direct upgrades from OCP V3.2.4 and later versions to the current version are supported.

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

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

Supported OceanBase Database versions

OCP V4.3.5 supports the following OceanBase Database versions:

• OceanBase V2.2.76 & 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 product features

Basic O&M

• Arbitration Service:

  • Supports high availability for arbitration services through arbitration service groups, ensuring continuous and stable service delivery by OceanBase.
  • Supports batch operations on arbitration services, including replacing arbitration services, associating with new clusters, and disassociating, improving user efficiency.

• Cluster management:

  • Added support for configuring automatic tenant replica scaling in zone scenarios, enhancing user productivity.
  • Added Start Time and Online Duration information for clusters and OBServer nodes, facilitating observation of database service capabilities. Display of Start Time and Online Duration is temporarily unavailable in cluster takeover scenarios.
  • Resource Management > Unit Distribution now supports displaying System_Memory / 500 Tenants.
  • When OceanBase is V4.X, Compactions supports displaying the records of the last three major compactions.

• Tenant Management:

  • Supports creating databases and usernames that contain the two special characters - and _. The character <code>_</code> is a MySQL wildcard. Be sure to pay attention to the authorization scope to avoid unauthorized access.
  • When OceanBase Database is V4.X, Compactions displays the records of the last three major compactions.

Performance Monitoring

• When OceanBase Database is V4.2.5 or later and the tenant is in MySQL-compatible mode, monitoring capabilities for OBKV-Redis instances are added, including QPS and Response Time.
• The monitoring dashboard supports importing/exporting Grafana/OCP monitoring metric data in JSON format, facilitating user monitoring of OceanBase databases.
• When OBProxy is V4.3.0 or later, monitoring capabilities for OBProxy RPC ports are added, including RPC Sessions, RPC Requests, and RPC Request Time.

Inspection Service

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

Backup and Recovery

• When OceanBase Database is V4.X, log backup tasks support pause/resume capabilities.
• During data recovery, the system's supported display interval is extended from the last 7 days to the last 180 days.
• The recovery task module adds a copy feature, allowing users to copy completed recovery tasks and modify some parameters as needed. This reduces repetitive work and significantly improves operational convenience and efficiency.

Open API

• Opens two Open APIs for starting and stopping OBProxy.
• Opens over 20 Open APIs for the arbitration service and service groups.

Platform Features

• O&M Configuration: Supports visual configuration of CPU/memory size used by OCP Agent at both cluster and host dimensions.
• Software Package Management: Supports batch uploading of software packages, improving operational convenience and efficiency.
• Log Services: When OceanBase Database is V4.2.3 or later (excluding V4.3.0), adds support for observer.log log compression.

Product Optimizations

Cluster Management

• When deleting a cluster, prompts users to clean up all data and log backups under that cluster, preventing unnecessary data from occupying storage space.
• When creating a cluster in OceanBase Database V4.X or later, the default system_memory/500 tenant setting is 0 MiB, enabling the system to allocate system_memory as needed.
• In primary/standby tenant scenarios, when upgrading a standby cluster, prevents the standby tenant from being two or more database versions higher than the primary tenant.

Tenant Management

• When deleting a tenant, prompts users to clean up all data and log backups under that tenant, preventing unnecessary data from occupying storage space.
• Supports batch adding/modifying IPv4 addresses for a tenant's allowlist. For example, xxx.xxx.xxx.1-3 indicates the three IP addresses xxx.xxx.xxx.1, xxx.xxx.xxx.2, and xxx.xxx.xxx.3, with only the last segment supporting a range.

OBProxy Management

• Adds a parameter template feature, providing two default parameter templates: 4.2.1 Default Parameter Template and Columnstore Replica Default Parameter Template.
• When creating an OBProxy cluster, moves the version selection before entering the root@proxysys password, preventing user misoperation in some business scenarios.
• The load balancing page implements the ability to add, display, and edit remarks.

Others

• Host management: Supports initializing hosts by product type (OceanBase / OBProxy).

• Binlog Service:

  • The real client IP address is displayed in Binlog Instance > Subscription Connections.
  • Added a parameter template feature, providing five default performance parameter templates: Default Performance Parameter Template, Intermediate Performance Parameter Template, Advanced Performance Parameter Template, Super Performance Parameter Template, and Top Performance Parameter Template.

• Performance Monitoring:

  • When the user monitoring period is set to more than 3 days, the monitoring chart displays 1,440 monitoring points, improving the accuracy of trend and characteristic analysis of monitoring data.
  • Optimized the selection logic for Custom Time in Performance Monitoring, enhancing the convenience of setting query time.

• Alert Center:

  • Added monitoring metrics in Alert Rules > Basic Settings, facilitating troubleshooting based on monitored metrics.
  • When muting alert targets, you can now use Tag to mute specific metrics.

Key feature overview

High availability of arbitration service

OceanBase Database V4.1 provides the arbitration service capability. With its significant advantage of low resource consumption and strong support for multi-clusters, the arbitration service has successfully created a lower-cost high availability solution for OceanBase Database, such as the 2F1A/4F1A architecture. Through this architecture, enterprises can ensure excellent high availability of the database system while effectively controlling resource costs, greatly improving the cost-effectiveness of the system. However, it is undeniable that the arbitration service has the potential for single-point-of-failure during operation. If an arbitration service fails, the high availability of the associated OceanBase cluster will inevitably degrade during the fault duration, which may negatively impact business continuity and stability. To effectively address this challenge, by building an arbitration service group, the system enables rapid switchover to another healthy arbitration service node within seconds when a node in the group fails and the replacement conditions are met, based on the priority settings. This maximizes the stable operation of OceanBase clusters under various complex circumstances and ensures business continuity.

Usage instructions:

• The versions of arbitration services within the same arbitration service group must be consistent.
• It is recommended to have at least two arbitration service addresses within a single arbitration service group.
• After an arbitration service switchover is completed, you must reconfigure the association between the cluster and the arbitration service based on your actual business situation to prevent any one arbitration service from becoming overloaded.
• Arbitration service groups and recovery plans: There is no functional conflict between the exit of the OBServer process of an arbitration service and its automatic restart by a recovery plan. That is, when an arbitration service fails, it can be automatically restarted by a recovery plan, but it will also be replaced if it meets the replacement conditions of its arbitration service group.
• Supports four main operations: creating a service group, upgrading a service group, editing a service group, and deleting a service group.

Optimization of backup strategies in OceanBase Database V4.x

• The ability to perform batch operations on tenant backup strategies as a cluster-level backup strategy:

  • Creating a cluster-level backup strategy only takes effect for tenants that have not set a tenant-level backup strategy.
  • When deleting a cluster-level backup strategy, the system will by default delete both the cluster and tenant backup strategies and disable log backup at the tenant level.

• Support disabling log backup in both cluster and tenant backup strategies. The system enables log backup by default before data backup and disables it after data backup, primarily to address the issue of excessive log backup size in some business scenarios.

• Enabling/disabling log backup in cluster/tenant backup strategies has the highest priority. Even if you manually disable/enable log backup, the system will default to the setting specified in the backup strategy.

• When editing cluster or tenant backup strategies, storage configuration options are grayed out by default, meaning you cannot change the storage path or the corresponding object storage AccessKey and SecretKey, to avoid causing log archiving startup failures or data backup failures.

• When no cluster or tenant backup strategy is available, the system records the log backup status. If log backup is not enabled, the system will enable it before data backup and disable it after data backup when you manually initiate a backup. If log backup is enabled, it will remain enabled after data backup.

Fixed issues

OCP V4.3.5 mainly fixes the following issues:

• Fixed the issue where the cluster list could not be displayed when a cluster was unavailable.
• Fixed the false alert issue caused by a failed location cache.
• Fixed the issue where data size was incorrectly displayed in table statistics.

Known issues

Version requirements

Hardware requirements

OCP-Server can be installed on physical servers or run in Docker containers. OCP-Server supports high-availability deployment with multiple nodes.

The minimum hardware requirements for an OCP-Server node are listed in the following table.

OCP-Agent consumes very few resources and has no specific hardware requirements for the installation node.

Operating system requirements

The operating system requirements for installing the OCP server (including OCP-Agent) are listed in the following table.

Client requirements

Users typically access OCP services through a web browser. The client requirements are as follows.

If you need to access OCP from a device running iOS, the version requirements are listed in the following table.

For the best user experience, we recommend using a display with a resolution greater than 1440 × 810.