OCP V4.4.1

V4.4.1 BP2

Version information

• Version: V4.4.1 BP2

• Previous version: V4.4.1 BP1

• Release date: March 26, 2026

Product behavior changes

Fixed some known issues.

V4.4.1 BP1

Version information

• Version: V4.4.1 BP1

• Previous version: V4.4.1

• Release date: March 12, 2026

New features

• Added alert monitoring for session kill failure scenarios with the ob_tenant_session_kill_delay metric and automated obstack stack information collection. Supported OceanBase versions: [V4.2.1.6, +∞).
• Added OBServer log-based alerts and automated obstack stack information collection for tenant queue full scenarios. Supported OceanBase versions: [V4.2.1.6, +∞).
• Added automated obstack stack information collection for ARM architecture environments. Supported OceanBase versions: [V4.2.1.6, +∞).
• Designed a standardized plugin interface (SPI) for TDE, providing a unified access solution for third-party cryptographic device manufacturers and significantly reducing adaptation complexity and cost.

Major bug fixes

Fixed several known issues.

Open issues

V4.4.1

OCP 4.4.1 is now available! This version brings comprehensive upgrades to the core capabilities of the OceanBase cluster management platform, providing enterprise users with a more stable, efficient, and secure database management experience.

Key features:

• Core capability enhancements: Supports core capabilities such as rapid test environment setup via standby tenant cloning, multi-source data integration through external tables, unified data views via ODPS Catalog, custom business logic via Java UDFs, and dynamic resource adjustment across asymmetric zones.
• Intelligent monitoring upgrade: Supports alert overview and intelligent interpretation for over 200 alert types, helping users identify alert patterns and improve alert handling efficiency.
• Security capability strengthening: TDE encryption now supports KMS services from third-party vendors such as 3W Security and Jiangnan Tianan.
• Enhanced platform-based O&M: Adds scheduled O&M task automation and OCP self-monitoring capabilities to meet the standardized and automated requirements of enterprise-level O&M.

Version information

• Version: V4.4.1

• Previous version: V4.4.0 BP3

• Release date: February 9, 2026

• Supported upgrade path:

  • Currently, only 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.4.1 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

• OceanBase V4.4.x

Key feature overview

JVM environment dependency service

Starting from V4.3.5 BP1, OceanBase has achieved seamless integration between the C++ and Java ecosystems through the Java Native Interface (JNI) bridge framework. Based on this JNI framework, OceanBase fully supports features such as ODPS external tables, HDFS external tables, Java UDFs, ODPS Catalog, and MySQL external table plugins. This ensures users can directly access Alibaba Cloud MaxCompute data warehouses and distributed file systems, and leverage user-defined functions written in Java for more flexible data processing and integration capabilities.

To reduce user deployment and operational complexity, OCP provides full lifecycle management capabilities. During cluster installation, deployment, and operational management phases, it supports operations such as uploading JAR packages, selecting supported service types, configuring JVM memory, checking JAR package compatibility during upgrades, automatically starting services during cluster scaling, and flexibly changing or disabling services.

Through OCP's visual operation and maintenance capabilities, the deployment threshold and users' daily operational burden can be significantly reduced. This technical solution retains the high-performance advantages of OBServer C++ while integrating the rich resources of the Java ecosystem, truly achieving a technical balance of "high performance, easy management, and strong scalability," providing solid technical support for enterprises to build modern data platforms.

Considerations:

• Enabling or disabling the JVM environment dependency service requires restarting the cluster.
• Ensure that each host in the cluster has sufficient reserved memory resources to guarantee stable service operation and avoid exceptions caused by insufficient memory.
• You must upload the required jar package libraries for service dependencies via the software package management tool in advance to ensure OBServer can load and use them properly.
• The JVM environment dependency service depends on the Java environment. If any machines in the cluster have not yet been configured with a Java environment, please configure it yourself and ensure the JDK meets the following requirements:
  • Hosts with x86/x86_64 architecture must install JDK 11 or later.
  • Hosts with ARM64 (aarch64) architecture must install JDK 15 or later.

Version information:

Different services have different requirements for the OceanBase cluster version:

Scheduled tasks

In an increasingly complex database operating environment, OceanBase Database ensures system stability by periodically initiating major compactions and collecting statistics within specific time windows. However, the database is always in a state of dynamic change—continuous minor compactions by tenants and frequent DML operations on tables constantly update statistics. In some extreme scenarios, due to the characteristics of the LSM tree architecture, if data updates are not detected in time, they may cause significant "read amplification" effects. Meanwhile, outdated statistics can severely impair the query optimizer's accurate judgment of execution plans, ultimately leading to increased overall database response latency and threatening business continuity.

To address this challenge, OCP introduces the scheduled task management feature. This feature leverages an intelligent scheduling engine to enhance the automation level of operational maintenance. Users can flexibly configure execution strategies for various key tasks based on business operation patterns, including tenant major compaction, post-major compaction statistics collection, and table-level statistics collection. Users can set scheduling strategies and expiration strategies based on business operation patterns, aligning operational timing more closely with business rhythms. Additionally, OCP provides comprehensive full-lifecycle task management capabilities, allowing you to easily enable or disable scheduled tasks, support forced execution, parameter editing, task copying, and deletion, and view detailed task execution records at any time. Through automated scheduling and intelligent optimization, OCP scheduled tasks ensure stable and efficient system operation, helping users build a smarter, more adaptive new operational maintenance paradigm.

New features

Basic operations and maintenance

• Cluster management:

  • Supports enabling or disabling the JVM environment dependency service, facilitating the use of features such as ODPS external tables/HDFS external tables/Java UDF/ODPS Catalog/MySQL external table plugins.
  • For scenarios involving adding zones or upgrading clusters, supports selecting different software package types (EL7/EL8/AL8) at the zone level. Also supports smooth upgrades from clusters deploying EL8-type software packages to EL7/AL8.
  • The transparent data encryption (TDE) feature is now compatible with KMS services from third-party vendors such as SMIC and Jiangnan Tianan, providing users with a more robust data protection solution. Supported OceanBase versions include: [V4.2.5.4, V4.3.0.0), [V4.3.5.2, +∞).
  • Supports configuring the port and specifications of the OCP Agent when taking over a cluster.

• Tenant management:

  • Supports the asymmetric zone feature, enabling differential configuration of the number of units for tenants across different zones. This feature has the following limitations:
    • The number of full-featured replica units for a tenant within each zone must not exceed two types.
    • Supported OceanBase versions include [V4.2.5.5, V4.3.0.0), [V4.4.2.0, V4.5.0.0).
  • Supports standby tenant cloning, meeting business scenarios where production and test environments in specific industries belong to the same cluster and require frequent DDL changes.
  • Supports setting a specific collation when creating an Oracle-compatible tenant.
  • Replica details support deleting specified units. Supported OceanBase versions include: [V3.0.0.0, V4.0.0.0).
  • Replica details support deleting specified unit groups. Supported OceanBase versions include: [V4.0.0.0, +∞).

• Host management: Supports configuring the port and specifications of the OCP Agent when adding a host.

Monitoring and alerts

• The alert overview feature is supported, providing comprehensive alert statistics and analysis capabilities. It supports analysis from multiple perspectives such as time and type, helping users deeply explore alert patterns and achieve proactive operation and maintenance.
• The AI assistant supports intelligent interpretation of over 200 alert types, helping O&M personnel quickly understand the meaning of alerts and reducing alert analysis time. When using this feature, ensure that OCP's MonitorDB is V4.3.5 BP3 or later.
• Vector memory metrics are supported: size occupied, size used, usage limit, usage rate display, and vector usage rate alert capability. The supported OceanBase versions are [V4.3.5.3, V4.4.0.0), [V4.4.1.0, +∞).
• Aggregation of recovery messages can be set up in the alert channel to reduce the number of recovery messages.
• A resolution function has been added to the details page for alerts that cannot be automatically eliminated.
• Support for Slack-type alert channels has been added, making it convenient for the system to push alert information to specified Slack workspaces.

Disaster Recovery Management for Primary and Standby Tenants

• Flexible configuration capabilities based on network and archive modes are supported in cascading and one-primary-multiple-standby scenarios, facilitating the construction of more suitable data synchronization solutions.
• When the primary tenant has no standbyRO user, users can manually set the standbyRO password.
• Displaying/copying the original primary tenant service name is supported during disaster recovery switchover, making it convenient for users to copy the original primary tenant service name during fault drills, thereby keeping the connection string unchanged.

O&M Management

Scheduled task management is supported, including creating scheduled O&M tasks for task types such as tenant merging and statistics collection, and supporting O&M operations such as editing, copying, and viewing related tasks.

Binlog Management

When creating a Binlog cluster, setting the MetaDB access address and port is supported, avoiding single-node failure risks and enhancing system high availability.

Backup and Recovery

• Setting the advanced attribute checksum_type for Alibaba Cloud Object Storage Service (OSS) is supported. Valid values are md5 (default) or no_checksum.
• Setting the Write Once Read Many (WORM) compliance retention policy for Alibaba Cloud Object Storage Service (OSS) is supported, meeting users' needs to save and use data in an indeleterable and tamper-proof manner.
• Viewing automatic cleanup records for physical backups (within the last 90 days) is supported.

Platform Capabilities

System Management supports displaying over 10 monitoring metrics for OCP itself, as well as alerting when the status is abnormal.

Product Optimization

Cluster Management

• Added display of software package types (EL7/EL8/AL8) in the Overview > Zone List section.
• Introduced a pre-check step before creating a cluster, allowing users to troubleshoot and resolve potential blockers in advance.
• Added a risk warning for kernel temporary versions: "The current cluster is built based on an informal software package (POC or for debugging purposes). This version has not undergone comprehensive testing and verification, and may contain compatibility vulnerabilities, functional defects, or security risks, which could lead to service anomalies or data corruption. Additionally, this cluster does not support upgrades to the official version. Please ensure you use the officially released version to guarantee system stability." The supported OceanBase version range is [V4.2.1.0, +∞).
• Added a prompt on the OBKV/Redis/HBase performance monitoring page: "In Cluster Overview > More > O&M Configuration > Parameter Management > Performance Monitoring Parameters, confirm whether the value of monagent.pipeline.obkv.collect.disabled is false."
• Fixed an issue where, in specific scenarios, the displayed OCP data disk size was still datafile_maxsize instead of datafile_size when datafile_next=0. This ensures the GUI display aligns with the actual creation logic.

Tenant Management

• Major Compaction Management: Added a prompt for standby tenants regarding major compaction settings: "Standby tenants do not support independent major compaction. Setting the major compaction time only affects the scheduling time after they are converted to primary tenants."
• Database Management: Creating databases in MySQL-compatible mode now supports the REFERENCES and EXECUTE privilege types.
  • References privilege is supported for OceanBase versions: [V4.2.4.0, V4.3.0.0), [V4.3.3.0, +∞).
  • EXECUTE privilege is supported for OceanBase versions: [V4.2.2.0, V4.3.0.0), [V4.3.2.0, +∞).

Host Management

Added a timeout parameter ocp.host.clockdiff.timeout.millis for executing the clockdiff command. The default value is 30 seconds, to prevent failures in pre-check steps under special circumstances.

OBProxy Management

Added display of software package types (EL7/EL8/AL8) on the OBProxy cluster Overview page.

Binlog Service

• Introduced a pre-check item when creating a Binlog cluster, helping users troubleshoot and resolve potential blockers in advance.
• Supports displaying the access address of a Binlog cluster on its Overview page.

Other

• Optimized the management of OceanBase primary and standby tenants across multiple OCP clusters in different time zones, ensuring correct time display in different regions and guaranteeing cross-border business continuity.
• In System Management > User Management, user and role names now support hyphens (-).
• In the Alert Center, added optional text fields in the recipient field for Alert Channel > Create Channel > Custom Script to avoid affecting customer configurations. Editing/copying detection rules for materialized view-related alert rules is prohibited.
• In Backup and Recovery, supports setting the timeout period for OCP Agent to parse backup sets via the backup.dump.physical.file.timeout parameter. The default value is 30 seconds.

Product Behavior Changes

"Autonomous Service" has been renamed to "Diagnostic Service".

Major Bug Fixes

OCP V4.4.1 primarily fixes the following issues:

• Fixed the issue where the error "Failed format number, input string: 2881;62888" occurred in logs after a host went offline.
• Fixed the issue where the error "token not found" was reported when upgrading OCP-Agent failed.
• Fixed the issue where the error "No enum ParameterType." was reported when upgrading OCP-Agent failed.
• Fixed the issue where the mc_ob_tenant table was not updated after retrying the Create ob tenant subtask during tenant creation.
• Fixed the issue where the self-starting file ocp_agent.service was missing after installing the OCP-Agent tar package.
• Fixed the issue where OCP tenants timed out during the PreCheck phase after a failover when simulating network disconnection between two IDCs.
• Fixed the issue where the ADMIN_VIEWER role could not access resources across organizations.
• 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).

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 across multiple nodes.

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

OCP-Agent consumes minimal 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.