What's New

This topic describes the features of OceanBase Admin Toolkit (OAT) V4.3.0.

New features

• Upgrade features:

  • OAT V4.3.0 supports rolling upgrades of OceanBase Cloud Platform (OCP) V4.3.0 and later.
  • OAT V4.3.0 supports upgrades of MetaDB V4.x on a GUI.

• OAT V4.3.0 supports rollback of OCP, OceanBase Developer Center (ODC), and OB Sharding on a GUI. You can roll each of these services back to the previous version in the following scenarios:

  • The service fails to be upgraded by using OAT and the issue persists. In this case, you can create a service rollback task on the Mission Center page.
  • The service is upgraded by using OAT. However, an error occurs in the service of the new version.

• Resource change features:

  • You can add nodes, replace nodes, and modify the resource specifications of existing nodes for the Network Load Balancer (NLB) component. Note that single-node NLBs do not support node replacement.
  • You can modify the resource specifications of the SQLAuditStore component.
  • You can add nodes, remove nodes, replace nodes, and modify the resource specifications of existing nodes for OB Sharding resources by specifying the odpserver or odpconsole configuration. In earlier versions, you can perform these operations only by specifying the odpserver configuration.

• OAT V4.3.0 supports the in-depth inspection feature. For more information, see Overview.

Optimized features

• The Custom Installation Path option is added to the following pages. By default, the option is disabled.

  • The initialization settings section of the Add Server dialog box.
  • The Modify Server Usage page.

• After you choose Server Initialization > Disk Initialization or Server Maintenance > Disk Initialization, you can specify the file system type on the page that appears.

  1. The Specify the file system type drop-down list is available. Valid values: xfs, ext4, and auto. Default value: auto.
  2. You can specify a file system type for each disk volume group (VG).

• The time zones of services and components are consistent with the time zone of the operating system. If a service or component supports all time zones, the system mounts the time zone file of the server and configures the time zone of the service or component based on the file when you start a container.

• Airflow is upgraded from V2.5.3 to V2.8.4.

Supported services and components

The following table describes the services supported by OAT.

The following table describes the components supported by OAT.