OCP V3.3.1

#RNDate#2022-05-24

OceanBase Cloud Platform (OCP) has been upgraded to support SQL diagnostics and other features. In addition, the new version supports the decoupling of primary and standby databases and provides other optimizations.

V3.3.1

Version information

• Version: V3.3.1

• Previous version: V3.3.0

• Version release date: May 24, 2022

• Supported upgrade path: You can directly upgrade OCP V2.3.x and later to this version. For OCP V2.3.0 and earlier, you must first upgrade to V2.3.x before upgrading to this version.

Supported OceanBase Database versions

OCP V3.3.1 supports the following OceanBase Database versions:

• OceanBase V1.4.x

• OceanBase V2.1.x

• OceanBase V2.2.x

• OceanBase V3.1.x

• OceanBase V3.2.x

New features

• VPC visual management

  • Added the ECS host type. You can select the ECS host type in the host list, when you import a host, or when you create or scale out an OceanBase cluster or an OBProxy cluster.

  • Added the network attribute display in the frontend page for scenarios such as hosts, OceanBase clusters, and OBProxy clusters.

  • Added the option to filter hosts by network type in the maintenance scenarios of OceanBase clusters and OBProxy clusters.

• Multi-condition alert feature

  • You can configure multiple alert expressions for monitoring metrics in the command-line interface (CLI). The expressions support the logical operators AND and OR.

  • You can display multiple monitoring charts on the details page of an alert for multiple monitoring metrics.

  • When you modify an alert for multiple monitoring metrics in the frontend page, the system displays a prompt indicating that the alert cannot be modified.

  • Integrated OAS alerts for seamless interoperability.

• OAS data query capabilities

  • Enhanced the monitoring query capabilities to better support OAS. The following multi-condition expressions and the ROUND() function are supported:

    • = (equivalent to:)

    • !=

    • =~ (regular expression match)

    • !~ (non-regular expression match)

  • Added the collection of kern.log logs for the log trace feature.

  • Added the collection of several monitoring data items, such as io_await and partition_iutil, to meet the requirements of OAS.

• Internationalization

  The documentation supports both Simplified Chinese and English. It is adapted to different language environments to ensure an internationalization experience.

Fixed issues

OCP V3.3.1 fixes the following issues:

• The FullGC issue under high pressure (20000 QPS).

• The error that occurs when an alert is reported after a sampling strategy is deleted during backup and restore.

• The error that occurs during the agent upgrade step when OCP is upgraded from V3.2.3 to a higher version on an ARM architecture.

• The error that occurs when you upgrade ob2230 to ob3230 by using OCP V3.3.0.

• The issue where a read-only cluster can modify tenant replicas.

• The false alert issue for the NTP service in a container environment.

• The issue where the Primary Zone information of a tenant is not updated.

• The issue where you cannot create a tenant on ob1479 by using OCP.

• The issue where the Python alert script template is outdated.

• The issue where the sys tenant has a long-term SlowSQL alert.

• The issue where the alert redirection logic is incorrect.

• The issue where the sum of the response ratio in SQL diagnostics is not 100%.

• Other issues in SQL diagnostics, monitoring, and alerts under specific conditions.

• Some frontend page interaction issues.

Known issues

Limitations

• Hardware requirements

OCP-Server can be installed on a physical server or in a Docker container. OCP-Server supports multi-node high availability deployment.

The following table describes the minimum hardware requirements for OCP-Server nodes.

OCP-Agent occupies very little resources. Therefore, no special hardware requirements are imposed on the installation node.

• Operating system requirements

The following table describes the operating system requirements for installing OCP (including OCP-Agent).

• Client requirements

General users usually access OCP by using a Web browser. Therefore, the following table describes the client requirements.

If you want to access OCP by using a device running the iOS operating system, the following table describes the requirements.

We recommend that you use a display with a resolution greater than 1440 x 810 for the best user experience.

V3.3.1 BP

Version information

• Version: V3.3.1 BP

• Previous version: V3.3.1

• Version release date: July 8, 2022

• Supported upgrade path: You can directly upgrade OCP V2.3.x and later to this version. For OCP V2.3.0 and earlier, you must first upgrade to V2.3.x before upgrading to this version.

New features

• Added the client port information to the session management page.

• Added the I/O statistics to the AWR report.

Fixed issues

OCP V3.3.1 BP fixes the following issues:

• The issue where the SSH latency is displayed as undefinedms in the host time of the cluster health check.

• The false alert issue for the server CPU system usage.

• The issue where a large number of SQL IDs are generated on the SQL diagnostics page, causing slow queries.

• The issue where the ocp-obcloud-service module is missing in the OCP V3.3.1 pom file.

• The issue where the initialization of OBConnector times out because the initialization is performed in a single thread.