OCP V4.0.3

#RNDate#2023-03-03

V4.0.3 BP2

Version information

• Version number: V4.0.3 BP2

• Previous version: V4.0.3 BP1

• Version release date: April 17, 2023

Bug fixes

• Optimized the performance of second-level monitoring to improve stability on low-configuration hosts.

• Fixed the issue of inaccurate resource trend data when OceanBase Database is V4.1.0.

• Fixed the issue of failed collection of a specific OceanBase metric, which does not affect product usage.

V4.0.3 BP1

Version information

• Version number: V4.0.3 BP1

• Previous version: V4.0.3

• Version release date: April 4, 2023

Bug fixes

• Optimized the issue where an error is reported after logging in to OCP when the user does not have the Overview page permission.

• Fixed the issue where offline cluster backup files cannot be parsed.

• Fixed the issue where AK/SK permissions are leaked.

• Modified the Fastjson version to nonautotype.

• Fixed the issue where primary/standby database switchover fails in specific scenarios.

V4.0.3

The main goal of OCP V4.0.3 is to integrate with the OceanBase Sharding platform and support taking over the OBProxy service under OceanBase Sharding. You can configure and manage alert and log query services for OceanBase Sharding on OCP, leveraging the OCP product foundation to reduce the time spent on repeated configurations.

Version information

• Version number: V4.0.3

• Previous version: V4.0.2

• Version release date: March 3, 2023

• Supported upgrade path:

  • OCP V3.2.4 and later can be directly upgraded to the current version.

  • OCP V2.3.x and later, but earlier than V3.2.4, must be upgraded to OCP V3.3.4 first.

  • OCP V2.3.0 and earlier must be upgraded to OCP V2.3.x first, and then to OCP V3.3.4.

Supported OceanBase Database versions

OCP V4.0.3 supports OceanBase Database of the following versions:

• OceanBase V1.4.x

• OceanBase V2.1.x

• OceanBase V2.2.x

• OceanBase V3.1.x

• OceanBase V3.2.x

• OceanBase V4.x

New features

• Integration with OBSharding

  Note

  Only OBSharding V3.2.6 and later are supported. The corresponding OAT version is V4.1.0 and later.

  • OCP allows you to create an OBProxy cluster in OBSharding mode by using API calls.

  • In OBSharding mode, an OBProxy cluster can take over the OBProxy service in OBSharding mode.

  • Based on the existing OBProxy alerts, the following alerts are added based on the characteristics of the OBSharding platform:

    • odp_sql_query_slow: the number of slow SQL queries exceeds the limit.
    • odp_sql_execute_failed: the number of SQL execution failures exceeds the limit.
    • odp_instance_compress_failed: OBProxy instance scale-down fails.
    • odp_instance_expanse_failed: OBProxy instance scale-up fails.

  • Log Service allows you to query and download logs of the OBProxy service in OBSharding mode.

• Password box

  The Password Box feature now supports the Test Credential feature, allowing you to test the validity of credentials with one click.

• Monitoring

  Tenant > Performance Monitoring has been added with distributed monitoring metrics (only supports OceanBase V3.2.4-bp1 and V4.1 and later):

  • The Performance and SQL section now includes a new SQL Execution Time monitoring chart, which contains local, remote, and distributed monitoring data.

  • The Transactions section now includes a new Transaction Response Time monitoring chart, which contains local and distributed monitoring data.

Feature enhancements

• Enhanced the permissions of the Overview page of the OCP console. Only the administrator can view the information on this page.

• Removed the OBProxy tab from the Password Box section, as it has no practical use.

• Improved the password update feature. After updating the root password of a cluster or tenant, the system will automatically update the corresponding credentials in the password box.

• Improved the error prompt when setting a custom installation directory during cluster creation. The error prompt is no longer displayed for some operating systems.

• Enhanced the cluster upgrade feature. OceanBase Database can now be upgraded from V4.0 to V4.1.

• Changed the default timeout alert threshold for data backup from 7 minutes to 60 minutes.

• Adjusted the default configurations of backup alerts in the OCP console:

  • base_backup_timeout: The alert level is changed from Critical to Caution.

  • backup_storage_capacity_over_threshold: The alert level is changed from Critical to Warning.

  • backup_storage_capacity_timeout_or_interrupted: The alert level is changed from Critical to Warning.

• Enhanced the alert statistics on the cluster overview page. You can view the statistics about the cluster, tenants, OBServer nodes, and log alerts in the cluster.

Bug fixes

OCP V4.0.3 fixes the following issues:

1. Optimized the cgroup control flow for OceanBase V4.x clusters by adding a control flow switch.

2. Optimized the CPU monitoring calculation method to better align with relevant standards.

3. Improved SSH compatibility by adding support for OpenSSH 8.8.

4. Fixed the issue where the number of active monitoring sessions occasionally exceeds the number of all sessions.

5. Fixed the issue where an upgrade from OCP V4.0.1 to V4.0.2 may fail due to timeout if historical data exists.

6. Fixed the issue where the system generates alerts continuously due to a large number of offline hosts during OCP restart.

7. Fixed the issue where modifying a deployed OCP console from a single-zone deployment to a multi-zone deployment fails.

8. Fixed several frontend display issues.

Known issues

Limitations on version usage

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 minimum hardware requirements for an OCP-Server node are described in the following table.

OCP-Agent itself consumes few resources and does not have specific hardware requirements.

Operating system requirements

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

Client requirements

Generally, users access OCP services through a web browser. Therefore, the following requirements apply to clients.

If you need to access OCP services using an iOS device, the following requirements apply.

For the best user experience, we recommend that you use a display with a resolution greater than 1440 × 810.