OCP V4.4.2 is officially released! This upgrade fully adapts to the strong sync mode between primary and standby instances and significantly enhances monitoring and alerting capabilities, delivering a more stable, efficient, and secure database management experience for enterprise users.
Key features:
- Primary-standby synchronization: Tenant-level primary and standby databases support two protection modes: Maximum Availability and Maximum Protection, helping users build a more comprehensive and reliable disaster recovery solution.
- External integration: Supports visual integration of monitoring data with Prometheus, facilitating the reuse of existing infrastructure and reducing the workload on the OCP system itself.
- AI-enhanced assistance: Based on user inquiries, intelligently recommends three highly relevant question options to help users clarify their needs, improving answer accuracy and user satisfaction.
Version information
Version: V4.4.2
Previous version: V4.4.1 BP2
Release date: April 28, 2026
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.4.2 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
OceanBase V4.5.x
OceanBase V4.6.x
Key feature overview
Primary-standby strong synchronization (Experimental feature)
To meet stringent requirements for high availability and data consistency in business scenarios, OceanBase Database achieves strong synchronization between primary and standby databases by implementing Maximum Protection or Maximum Availability mode. This provides more reliable and secure data services, meeting the high standard of RPO=0.
Features |
Maximum Protection Mode |
Maximum Availability Mode |
|---|---|---|
| Synchronization Mechanism | A transaction can return a commit success result to the client only after the redo logs on the primary database and all strongly synchronized standby databases have been successfully persisted. | Similar to maximum protection mode, a transaction is committed only after the redo logs are successfully persisted on both the primary database and the strongly synchronized standby database. |
| Availability Guarantee | When the strong-sync standby database becomes unavailable, the primary database automatically stops write services to prevent data inconsistency. | When a strong sync standby failure is detected, the system automatically downgrades to maximum performance mode to prioritize ensuring the availability of the primary database service. |
| Application scenarios | Financial core systems and transaction settlement systems that require extremely high data consistency. | Business systems with high requirements for availability and consistency. |
OCP provides comprehensive disaster recovery management capabilities, supporting the following key features:
- Mode management: Supports flexible switching between synchronous mode and protection mode, including changing from Maximum Performance to Maximum Availability or Maximum Protection, and changing from Maximum Availability or Maximum Protection back to Maximum Performance.
- Switching operations: Supports routine switching/batch routine switching, disaster recovery switching/batch disaster recovery switching, reducing operational complexity for users in disaster recovery and drill scenarios.
- Architecture adjustment: Supports primary-standby decoupling to meet flexible business deployment requirements.
- Visual monitoring: Displays primary-standby topologies, visually presenting architectures such as primary-standby, one-primary-multiple-standby, and cascaded architectures, along with synchronization status.
Notice
New features
Basic O&M
Cluster management: The Transparent Data Encryption (TDE) feature has been adapted to work with Jiangnan Keyu's KMS service, 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, +∞).
Monitoring and alerting
- Supports collecting arbitration service logs and triggering alerts based on log errors.
- OBProxy supports drilling down into monitoring metrics layer by layer, helping users quickly locate issues and gain an in-depth understanding of system status.
- Supports alerts for clog and hang log types, providing specific cause analysis and solutions to avoid business interruptions caused by these issues.
- When configuring alert muting for SQL-type alert rules (such as
oas_anomaly_sql_from_{*}), supports more filter tags, such as database name and username. - Supports alerts for missing primary logs in log streams. Supported OceanBase version range is: [V4.0.0.0, +∞).
- Supports configuring independent threshold parameters for different clusters for alert rules like
oas_anomaly_sql_from_{*}, ensuring monitoring strategies match the actual operational status of each cluster. - Monitoring charts support descending order display, making it easier to view performance bottlenecks.
Disaster recovery management
- Supports tenant-level primary-standby database protection modes Maximum Availability and Maximum Protection, facilitating the construction of more reliable disaster recovery solutions. Supported OceanBase version range is: [V4.4.2.1, +∞).
- Supports pausing/enabling log synchronization on the primary-standby tenant overview page, and adds attribute displays for status, protection mode, and protection level.
- Supports displaying historical latency information for primary-standby tenants on the cluster overview page, facilitating latency analysis over time.
- Improves the efficiency of performing batch routine switching in scenarios with 10+ tenants.
Platform capabilities
Security: Compatible with commercial versions of Tectia SSH Client/Server.
Notice
Subject to the constraints of the software license agreement, the related client must be downloaded and deployed by the user from official channels.
External integration: Supports visual integration of monitoring data with Prometheus, facilitating user reuse of existing infrastructure and reducing the load on OCP itself.
Product enhancements
Tenant management
Supports pre-check for unit scale-in to reduce the likelihood of business impact due to insufficient tenant memory.
OBProxy
Before migrating out OBProxy, checks whether the obproxy_config_server_url format complies with OCP specifications and prompts: OBProxy configuration server URL (obproxy_config_server_url) format validation failed. It is recommended to correct the configuration after migration. Note that a configuration change will cause a brief service interruption in OceanBase Database.
Binlog service
Optimized the status synchronization mechanism for abnormal logproxy processes in OCP to ensure the monitoring interface can display the corresponding status in real time and accurately when an exception occurs.
Other
- The OCP-Agent execution shell command is now specified as
/bin/bashby default, resolving the issue where scripts could not execute properly on some operating systems using other types of shells. - The OCP OpenAPI interface supports SHA256-based security signature authentication to prevent request tampering and unauthorized access.
- Added a schema attribute to tables within transparent data encryption (TDE) tablespaces.
- When setting the system model in External Integration > Large Model, the Rerank model supports being selected as empty.
- Added prompts on the Cluster Management > O&M Configuration > OCP Agent Resource Configuration, Host > Change OCP Agent Specification, and Host Management > Add Host pages: In high business load or stress test scenarios, it is recommended to upgrade the OCP Agent resource specification to prevent OOM or loss of monitoring data due to insufficient resources.
Product behavior changes
- Added three time ranges to the time selector on the Performance Monitoring page: Last 5 Minutes, Last 10 Minutes, and Last 7 Days. Removed the less frequently used Last 1 Minute option to improve user query efficiency.
- Removed the invalid alert rule
ob_log_server_hang_due_to_trx_lock.
Major bug fixes
The following issues are fixed in OCP V4.4.2:
- Fixed the issue where the OBProxy Client Connection Usage Exceeds Limit alert failed to trigger on some nodes in multi-node OCP mode.
- Fixed the issue where the
ob_adminparsing command generated by OCP Agent during recovery initiation was inaccurate. - Fixed the issue where tenant creation failed when the tenant parameter template contained the
max_allowed_packetparameter. - Fixed the issue where the data type for OceanBase data disks was incorrect in inspection reports.
- Fixed the issue where OBShell failed to start because the root@sys password contained special characters.
- Fixed the issue where the
monagent.limit.memory.quotaconfiguration did not take effect when collecting theob_cluster_arbitration_activemetric. - Added related operation prompts when canceling the upload of a software package.
- Fixed the inconsistency between the UI and label names for Credential Management in Chinese and English OCP interfaces.
- Fixed the issue where OCP-Agent automatically restarted abnormally due to inconsistent paths between those specified in
ocp_agent.serviceand the actual paths.
Known issues
None.
Version usage restrictions
Hardware requirements
OCP-Server can be installed on physical servers or run in Docker containers. OCP-Server supports high-availability deployment in multi-node mode.
The minimum hardware requirements for an OCP-Server node are listed in the following table.
Hardware |
Requirements |
|---|---|
| CPU | |
| Memory | Available Memory: 16 GiB |
| NIC | 10 Gbit/s NIC |
OCP-Agent consumes very few resources and has no specific hardware requirements for the installation node.
Operating system requirements
The following table describes the operating system requirements for installing the OCP server (including OCP-Agent).
Server Type |
Operating System |
Supported Versions |
|---|---|---|
| x86_64 | RHEL | 7.2 and later |
| x86_64 | CentOS | 7.2 and later |
| x86_64 | AliOS | 7.2 and later |
| x86_64 | openSUSE | 12 SP3 and later |
| ARM aarch64 | AliOS | 7.2 and later |
| ARM aarch64 | NeoKylin | 7.6 |
| ARM aarch64 | Huawei EulerOS | 2.0 SP8 |
| x86_64 | Debian | Debian GNU/Linux 11 (bullseye) |
| x86_64 | Ubuntu | Ubuntu 18.04.6 LTS |
Client requirements
Users typically access OCP services through a web browser. The client requirements are as follows.
Browser |
Minimum Version |
|---|---|
| Chrome | 88 |
| Firefox | 78 |
| Edge | 88 |
If you need to access OCP from a device running iOS, the version requirements are listed in the following table.
Operating System |
Minimum Version |
|---|---|
| iOS | 10 |
For the best user experience, we recommend using a display with a resolution greater than 1440 × 810.