OCP V4.0.3

#RNDate#2023-03-03

V4.0.3 BP2

Version information

• Version: V4.0.3 BP2

• Previous version: V4.0.3 BP1

• Version release date: April 17, 2023

Bug fixes

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

• Fixed the issue where resource trend data was inaccurate when OceanBase Database was V4.1.0.

• Fixed the issue where the collection of a specific OceanBase Database metric failed. This issue does not affect product usage.

V4.0.3 BP1

Version information

• Version: V4.0.3 BP1

• Previous version: V4.0.3

• Version release date: April 4, 2023

Bug fixes

• Fixed the issue where an error is reported when a user logs in to OCP without the Overview page permission.

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

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

• Changed the Fastjson version to nonautotype.

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

V4.0.3

OCP V4.0.3 is released to support the integration with the OceanBase Sharding platform. You can use OCP to take over the OceanBase Proxy service in the OceanBase Sharding platform. You can also configure and manage alert and log query services in the OceanBase Sharding platform on OCP. This way, you can reuse the OCP platform capabilities and reduce the time spent on repeated configurations.

Version information

• Version: V4.0.3

• Previous version: V4.0.2

• Version release date: March 3, 2023

• Supported upgrade path:

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

  • For OCP V2.3.x and later, V3.2.4, you need to upgrade to OCP V3.3.4 first.

  • For OCP versions earlier than V2.3.0, you need to upgrade to OCP V2.3.x first, and then to OCP V3.3.4.

Supported OceanBase Database versions

OCP V4.0.3 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

• OceanBase V4.x

New features

• Integration with the OBSharding platform

  Note

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

  • OCP supports creating an OBProxy cluster in the OBSharding mode by calling an API.

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

  • The following alerts are added to the original OBProxy alerts based on the features of the OBSharding platform:

    • odp_sql_query_slow: The number of slow SQL queries exceeds the threshold.
    • odp_sql_execute_failed: The number of failed SQL executions exceeds the threshold.
    • odp_instance_compress_failed: The scaling-in of an OBProxy instance fails.
    • odp_instance_expanse_failed: The scaling-out of an OBProxy instance fails.

  • Log Service supports querying, downloading, and viewing logs of the OBProxy service in the OBSharding platform.

• Password box

  The Password box feature now supports the Test Credentials feature, which allows you to test the validity of credentials with one click.

• Monitoring

  In the Tenant > Performance Monitoring section, new distributed monitoring items are added (only supported for OceanBase Database V3.2.4-bp1, V4.1, and later versions):

  • A new SQL Execution Time monitoring chart is added under Performance and SQL, which includes local, remote, and distributed monitoring data.

  • A new Transaction Response Time monitoring chart is added under Transaction, which includes local and distributed monitoring data.

Feature enhancements

• The Overview page of the platform is optimized to allow only administrators to view the platform overview.

• The OBProxy tab in the Password box feature is deleted because it has no practical use cases.

• The password update feature is optimized. After you update the root user password of a cluster or tenant, the system automatically updates the related credentials in the password box.

• The error prompt for unsupported custom installation directories during cluster creation is optimized.

• The cluster upgrade feature is optimized to support upgrading OceanBase Database from V4.0 to V4.1.

• The default timeout threshold for data backup alerts is adjusted from 7 minutes to 60 minutes.

• The default configurations for backup alerts in OCP are adjusted as follows:

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

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

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

• The alert statistics on the cluster overview page are optimized to support viewing statistics about clusters, tenants, OBServer nodes, and log alerts.

Fixed issues

OCP V4.0.3 fixes the following issues:

1. The cgroup control flow of OceanBase Database V4.x clusters is optimized, and a control flow switch is added.

2. The CPU monitoring calculation method is optimized to better align with relevant standards.

3. The SSH compatibility is optimized, and host compatibility with OpenSSH 8.8 is added.

4. The issue where the active value occasionally exceeds the all value in monitoring sessions is fixed.

5. The issue where upgrading OCP from V4.0.1 to V4.0.2 may fail due to a timeout when historical data exists is fixed.

6. The issue where restarting OCP generates alerts for a large number of offline hosts is fixed.

7. The issue where modifying a deployed OCP from a single-zone to a multi-zone deployment fails is fixed.

8. Other front-end display issues are fixed.

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 minimum hardware requirements for OCP-Server nodes are as follows:

OCP-Agent consumes very few resources and has no special hardware requirements for the installation node.

Operating system requirements

The operating system requirements for installing OCP-Server (including OCP-Agent) are as follows:

Client requirements

General users typically access OCP services through a web browser, so the client requirements are as follows:

If you need to access OCP services from an iOS device, the operating system requirements are as follows:

For the best user experience, we recommend using a display with a resolution greater than 1440 x 810.