OCP V4.5.1 is officially released! This upgrade strengthens daily management capabilities for complex production environments, focusing on resolving practical issues such as reliance on manual experience for high-risk operations, difficulty in layered planning for backup storage, and late detection of tenant capacity problems.
Key Highlights:
- Standard Operating Procedures (SOPs): Adds standard operating procedures, organizing complex, high-risk operations into savable, executable, and trackable maintenance tasks to reduce manual confirmation steps and operational omissions. Three built-in procedures include: rebuilding a standby tenant, enabling the arbitration service when a replica is abnormal, and reconstructing data after an OBServer failure.
- Separate storage for backup data and archived logs: OceanBase 4.x clusters support setting different storage locations for backup data and archived logs, allowing you to choose between file storage or object storage based on reliability, capacity, and cost.
- Data disk quota for units: Unit specifications in Shared-Nothing clusters support setting data disk quotas, which are displayed in the tenant and resource views. The system generates warnings and critical alerts when usage reaches 80% and 90%, respectively.
Key Feature Overview
Standard Operating Procedures (SOPs)
Adds standard operating procedures, organizing complex, high-risk operations into savable, executable, and trackable maintenance tasks to reduce manual confirmation steps and operational omissions.
The following procedures are built into this release:
- Rebuilding a standby tenant: Supports managed cross-OCP primary/standby tenant scenarios.
- Enabling the arbitration service when a replica is abnormal: Only supports clusters currently managed by OCP.
- Reconstructing data after an OBServer failure: Only supports clusters currently managed by OCP.
Maintenance personnel can view the execution progress of each step and retry if a step fails.
Separate storage for backup data and archived logs
OceanBase 4.x clusters support setting different storage locations for backup data and archived logs, allowing you to choose between 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 separate storage is required, it is recommended to complete the entire OCP upgrade before enabling the new configuration.
Data disk quota for units
Unit specifications in Shared-Nothing clusters support setting data disk quotas, which are displayed in the tenant and resource views. The system generates warnings and critical alerts when usage reaches 80% and 90%, 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.
Key Feature Overview
Standard Operating Procedures (SOPs)
Adds standard operating procedures, organizing complex, high-risk operations into savable, executable, and trackable maintenance tasks to reduce manual confirmation steps and operational omissions.
The following procedures are built into this release:
- Rebuilding a standby tenant: Supports managed cross-OCP primary/standby tenant scenarios.
- Enabling the arbitration service when a replica is abnormal: Only supports clusters currently managed by OCP.
- Reconstructing data after an OBServer failure: Only supports clusters currently managed by OCP.
Maintenance personnel can view the execution progress of each step and retry if a step fails.
Separate storage for backup data and archived logs
OceanBase 4.x clusters support setting different storage locations for backup data and archived logs, allowing you to choose between 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 separate storage is required, it is recommended to complete the entire OCP upgrade before enabling the new configuration.
Data disk quota for units
Unit specifications in Shared-Nothing clusters support setting data disk quotas, which are displayed in the tenant and resource views. The system generates warnings and critical alerts when usage reaches 80% and 90%, 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.
New features
For details, see OCP V4.5.1 Release Notes.
References
For more information about version releases, please follow our release notes: