OAT V4.4.0

Release purpose

To better assist users in operating OceanBase products, this OAT V4.4.0 version introduces significant upgrades in its O&M features: it now supports installation and deployment, rotation upgrades, and takeover operations in the primary region mode of OMS V4.3.1. Additionally, it includes the integration installation capability for the OBLens performance diagnostic tool.

Release overview

• Release date: 2025.11.07
• Previous version: V4.3.2 BP1
• Version: V4.4.0

New features

• Comprehensive support for installation, deployment, upgrades, takeover, and data refresh operations in the primary region architecture of OMS V4.3.1, adhering to the principle of single-point deployment for management services—only running in the primary region's OMS container.
• Support for installing and uninstalling the performance diagnostic tool OBLens, facilitating quick identification and resolution of complex issues.
• Enhanced system monitoring capabilities with the adoption of antsar replacing tsar during server initialization, providing more robust performance data collection features.

Bug fixes

• Fixed the issue where the synchronization task to OCP would succeed even if the synchronization operation timed out during server initialization.
• Fixed the issue where OCP, ODC, and OBSharding could not be rolled back in version rollback tasks.
• Fixed the issue where the config_os subtask should set Python soft links as needed during server initialization.
• Fixed the issue where OCP rolling upgrade tasks could not be rolled back.
• Fixed the issue where a quick installation error would occur if the server used a disk initialized but not all directories were mounted.
• Fixed the issue where an error would occur in the start_first_odc_container subtask when deploying ODC using NLB VIP in a Kylin V11 environment.
• Fixed the issue where an error would occur in the check_requirements subtask during OCP/ODC/InfluxDB/OMS installation: can not get timezone name from timedatectl.
• Fixed the issue where an error would occur in the start_metadb subtask when installing the MetaDB component on a UOS V20 1070e server due to the default automatic setting of the Asia/Beijing timezone.
• Fixed the issue where the check_ssh subtask incorrectly checked for clock offset during server initialization.
• Fixed the issue where the metadata recovery for the meta tenant would fail during OCP version rollback, but the rollback task would continue.
• Fixed the issue where the frontend incorrectly filtered servers based on their purpose during OBLB resource changes.

Considerations

OAT V4.x versions can only be upgraded in-place from OAT V3.2.0 or later. Ecosystem products deployed with earlier versions of OAT or Antman can be taken over to a newly deployed OAT instance using the "take over component" and "take over product" features.

Reference

Upgrade Guide