Release purpose
To better assist users in the O&M of OceanBase products, this release of OAT V4.3.1 introduces the resource change feature for OBLB and OBDNS, enabling the addition and replacement of nodes and the adjustment of node resource specifications for OBDNS. It also supports the use of different OceanBase clusters for Meta and Monitor tenants in OCP. By optimizing the resource change logic for products and components, the execution speed and stability of tasks have been significantly improved. Additionally, the minimum resource specifications for server initialization are now configurable, helping users achieve more diverse business scenarios and customization needs.
Release overview
Release date: 2025.03.03
Previous version: V4.3.0
Version: V4.3.1
New features
Supports resource change for OBDNS, including adding/replacing nodes (single-node OBDNS does not support node replacement) and modifying node resource specifications.
Supports resource change for OBLB, including adding/replacing nodes (single-node OBLB does not support node replacement).
Supports the use of different clusters for Meta and Monitor tenants in OCP.
Added system configuration items oat.server.min_cpu and oat.server.min_memory to configure the minimum resource specifications for server initialization.
Server initialization now supports automatic calculation and setting of team NIC speed and QDFS file system.
Bug fixes
Fixed an issue where resource change tasks for OBSharding using NLB/OBDNS as the load balancer failed.
Fixed an issue where changes to container specifications during resource change in odpconsole did not take effect.
Fixed an issue where script installation of oat in oat-all-in-one required timezone and internationalization compatibility.
Fixed an issue where the file_system_type was not passed when an error occurred during disk initialization.
Fixed an issue where resource change tasks for OBSharding could not be initiated when only new odpserver nodes were added.
Fixed an issue where port conflicts were not checked before initiating resource change or downtime upgrade tasks for OBSharding.
Optimized the performance of asynchronous tasks when managing a large number of servers.
Known issues
In OBLB resource change, the installation count and status are incorrect.
Occasionally, an error occurs during password encryption when creating OCP.
When using sudo privileges of a regular third-party user to add a host, the precheck step cannot correctly verify the ulimit -H -c setting.
Considerations
OAT 4.x versions can only be upgraded in-place from OAT 3.2.0 or later. Products deployed with older OAT or Antman can be taken over to a newly deployed OAT using the "Take Over Component" and "Take Over Product" features.
Upgrade guide
Supported products
Name |
Version |
Description |
|---|---|---|
| OCP | OCP V3.2.0 and later | |
| ODC | ODC V3.2.0 and later | |
| OMS | OMS V3.2.0 and later | |
| OBSharding | OB Sharding 3.2.4 and later | |
| MetaDB | OB4.2.1.7_OBP4.2.1.0/OB421_OBP421/OB2277_OBP329 | Built-in OBProxy version |
| OBDNS | OBDNS_20220806_1622 and later | Built-in etcd version |
| NLB | NLB 3.5.1, 4.0.0 | |
| InfluxDB | 1.8 | |
| OpenSearch | 3.3.2 | |
| OBLB | 1.4.0, 1.4.1 |