Release purpose
To better assist users in operating and maintaining OceanBase products, OAT V4.5.2 introduces full lifecycle management for the OAgent product, supports server initialization for the OB AI (storage-compute separation) architecture, and optimizes the DataPilot deployment scheme to a dual-tenant single-image mode. This further enhances the management capability and deployment flexibility for the OceanBase AI ecosystem.
Release summary
- Release date: August 28, 2026
- Previous version: V4.5.1 BP1
- Version number: V4.5.2
New features
Added management for the OAgent product, including:
- Install OAgent
- Upgrade OAgent (including upgrade pre-check)
- OAgent resource changes
- OAgent container operations
- Uninstall OAgent
Note
OAgent is a single-container, self-contained product that does not depend on MetaDB, tenants, or load balancing, and only supports single-node deployment.
Added new server usage purposes OB AI and Logservice for deploying OceanBase AI (storage-compute separation) architectures, including:
- OB AI: Suitable for dedicated OceanBase AI cluster deployment. Requires separate mounting of
/data/1(the observer-s local cache path, recommended with more than 3 times the memory) and/home/admin. - Logservice: Suitable for dedicated Logservice deployment. Requires separate mounting of
/data/logservice1(local storage path, recommended ≥ 100GB) and/home/admin. - OB AI and Logservice can be selected simultaneously, but not together with other server usage purposes. In an OB AI scenario, observers and Logservices may be co-deployed.
- OB AI: Suitable for dedicated OceanBase AI cluster deployment. Requires separate mounting of
Feature optimizations
Optimization of the DataPilot deployment scheme: Changed from dual-images to single-image deployment, removing the E2B image and independent Docker network configuration; added administrator password and S3 port parameters to the basic configuration; modified MetaDB configuration to dual-tenant mode, supporting both created MetaDB and other OB_MySQL types; added the option for created OBDNS in load balancing.
Added OAgent to the list of supported products for product and component resource changes, and container operations.
Considerations
Considerations for OAgent deployment:
- Some Docker versions (such as 18.x and earlier) may prevent the OAgent container from starting due to the seccomp security policy intercepting the
clone3system call. If this issue occurs, it is recommended to upgrade Docker to version 20.10.10 or later, or add the--security-opt seccomp=unconfinedparameter to the startup options. - The minimum supported version for OAgent is 1.6.0.
- Some Docker versions (such as 18.x and earlier) may prevent the OAgent container from starting due to the seccomp security policy intercepting the
Considerations for DataPilot upgrade:
- After upgrading OAT from an earlier version to the deployment solution of V4.5.2, the configuration of DataPilot has changed and a direct upgrade of DataPilot is not supported. You can use the GUI upgrade feature after uninstalling and reinstalling DataPilot.
Considerations on the usage of OB AI servers:
- In an OB AI scenario, observers and Logservices may be co-deployed. When co-deploying, you need to select both the OB AI and Logservice usage.
- The data disk path for OB AI is used for local caching by observers. It is recommended that the available space be more than three times the memory size, with 8 to 10 times being ideal.
- The data disk path for Logservice is used for local storage. A recommended space size is ≥ 100 GB.