OCP V4.5.1 enhances daily management capabilities for complex production environments, focusing on practical issues such as reliance on manual experience for high-risk operations, difficulty in layered planning for backup storage, and delayed detection of tenant capacity problems.
Version Highlights
Standard O&M Processes
Standard O&M processes are introduced, organizing complex, high-risk operations into saveable, executable, and traceable tasks, reducing manual confirmation steps and operational omissions.
The following processes are built-in this release:
- Rebuild a standby tenant
- Enable the arbitration service when a replica is abnormal
- Data reconstruction after an OBServer failure
O&M personnel can view the execution progress of each step and retry upon failure. Rebuilding a standby tenant supports managed cross-OCP primary/standby tenant scenarios; the other two processes only support clusters managed by the current OCP.
Separated Storage for Backup Data and Archived Logs
OceanBase clusters of version 4.x support setting different storage locations for backup data and archived logs, allowing you to choose file storage or object storage based on reliability, capacity, and cost. This capability covers backup strategies, immediate backup, backup scanning, and tenant recovery.
The original shared storage method remains unchanged. When using separate storage is required, it is recommended to complete the full OCP upgrade before enabling the new configuration.
Unit Data Disk Quota
Unit specifications in Shared-Nothing clusters support setting data disk quotas, and usage is displayed in tenant and resource views. The system generates warnings and critical alerts at 80% and 90% usage, respectively, facilitating capacity expansion or data governance arrangements before insufficient capacity occurs.
This quota is a soft limit; exceeding it does not interrupt business writes. It applies to OceanBase Database V4.0 and later.
Other New Features and Optimizations
- Standby tenants support setting log restoration latency, with latency status monitoring and alerts provided.
- Added Japanese-language interface, covering main product text such as alerts, monitoring, inspections, and parameter configurations.
- Expanded KMS compatibility for transparent data encryption scenarios, adding solutions from Alibaba Cloud Apsara Stack, Xin'an Century, and Jiangnan Keyou (financial), and improved HTTPS access capability for GEL KMS.
- Software packages support SHA256 verification, with added limits on the number and total capacity of uploads.
- Alert events now include resource tags, and long-tranction alerts supplement log stream information, making it easier to locate specific tenants and log streams.
- SQL query interfaces support specifying database users, facilitating queries based on existing account permissions.
- Added global backup information parsing and offline restore interfaces, facilitating automated restore process integration.
- Optimized OCP and Agent resource monitoring, real-time monitoring queries, and multilingual search experience.
Behavior Changes and Scope of Application
Behavior Changes
- Cloning of primary tenants is no longer supported; standby tenant cloning capability is unaffected.
- Added limits on the number and total capacity of software package uploads. The system prevents uploads when these limits are exceeded.
Scope of application
- Data and log separation storage applies to OceanBase clusters of version 4.x; OceanBase clusters of version 3.x continue to use the same storage location.
- The unit data disk quota applies to shared-nothing clusters, but not to shared-storage or OceanBase AI clusters.
- Enabling log restore latency is required for standby tenants in OceanBase Database V4.4.2.2 and later.
Major bug fixes
- Fixed issues in primary/standby tenant switchover, source adjustment during recovery, and delayed recovery scenarios, improving the stability of cross-cluster disaster recovery operations.
- Fixed problems in backup storage identification, log backup check, and certain recovery scenarios.
- Fixed anomalies in AI clusters and LogService during zone stop, key rotation, and task rollback.
- Fixed issues such as slow real-time monitoring queries, missing monitoring data on some hosts, and abnormal display of agent resource metrics.
- Fixed abnormal time types in query results for Oracle-compatible tenants, and index information being empty due to database name casing.
- Fixed issues with permission verification, operation object identification, task retry, and page display in SOP.
Open issues
Problem description |
Probability |
Solution |
|---|---|---|
| An exception occurred during parsing when initiating storage separation recovery in OCP V4.5.1. | Under specific conditions | Waiting for Background Task |
| Failed to initiate cluster-level tenant recovery in OCP V4.5.1 | Under specific conditions | Contact Technical Support |
Security vulnerability fixes
Fixed several permission verification, input validation, and sensitive information protection issues. It is recommended to upgrade to this version.
Upgrade method
For the upgrade method, refer to Upgrade documentation.