Release purpose
To better assist users in operating OceanBase products, this OAT V4.4.1 release introduces full lifecycle management for OAS, supporting installation, upgrade, version rollback, uninstallation, and resource changes. It also adds an arbitration service as a standalone server, offering flexible deployment and optimized resource allocation. High availability testing is introduced, and full lifecycle management for the arbitration service component is added, including creation, upgrade, data refresh, and takeover operations. OBClient, OpsToolkit, and other commonly used tools now support resource changes, allowing for node addition, deletion, and replacement to enhance operational flexibility.
Release overview
- Release date: 2026.02.06
- Previous version: V4.4.0
- Version: V4.4.1
New features
Added OAS management, including:
- Install OAS
- Upgrade OAS
- Version rollback
- Uninstall OAS
- OAS container operations
- OAS resource changes
Added Arbitration Service as a server purpose. The arbitration service is suitable for dedicated deployment, reducing server resource requirements and enabling Docker installation.
- On the Add Server page, the server purpose initialization configuration now includes Arbitration Service.
- On the Modify Server Purpose page, the server purpose now includes Arbitration Service.
- On the Initialize Disk page, the arbitration service software installation path and Docker root directory are added.
Added High Availability Testing in O&M Management. This feature currently supports three core test scenarios: process high availability testing, server high availability testing, and network card fault high availability testing. For more details, see Create High Availability Test.
Added support for the Arbitration Service component to facilitate management of the arbitration service in MetaDB. This includes:
- Create Arbitration Service
- Upgrade Arbitration Service
- Uninstall Arbitration Service
- Arbitration Service container operations
- Arbitration Service resource changes
- Data refresh
- Take over Arbitration Service
Added resource change capabilities for OBClient, OpsToolkit, SQL Diagnoser, Obdiag, OB-Loader-Dumper, Sysbench, and OBLENS tools, supporting the addition, deletion, and replacement of server nodes.
Feature enhancements
When creating MetaDB, you can now create an arbitration service under the arbitration service configuration.
On the Take Over/Refresh Data page for MetaDB, you can select Arbitration Service.
When selecting MetaDB configurations, you can now navigate to the Create MetaDB page.
During server initialization, OBWatcher is installed by default (copying the shell script to the server).
Note
If OBWatcher was not installed on the server before upgrading OAT to V4.4.0, you can use the general server purpose modification feature to re-run the server initialization task and install OBWatcher.
Considerations
When using OAS, note the following:
Takeover of OAS is not supported.
IPv6:
- OAS itself does not support IPv6, and MetaDB cannot be deployed using IPv6.
- OCP deployed using IPv6 is not supported.
- IPv6 usage in business clusters within OCP is not checked.
Time zone internationalization: OAS itself does not support time zone internationalization, but it can be associated with an OCP that does support it.
The following server purpose combinations are not supported:
- Arbitration Service + OB Server
- Arbitration Service + OB Product Service
- Arbitration Service + OB Server + OB Product Service
At present, you cannot associate an arbitration service with an existing MetaDB or modify the arbitration service associated with MetaDB. However, you can manually associate an arbitration service and refresh data for MetaDB in OAT.