OCP V4.0.3

V4.0.3 BP2

Version information

• Version: V4.0.3 BP2

• Previous version: V4.0.3 BP1

• Release date: April 17, 2023

Bug fixes

• Optimized second-level monitoring performance for more stable performance on low-configured hosts.

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

• Fixed an issue where data collection for a specific OceanBase 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

• Release date: April 4, 2023

Bug fixes

• Fixed an error that occurred after logging in to OCP when the user had no permissions for the Overview page.

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

• Fixed the issue of AK/SK permission leakage.

• Modified the Fastjson version to nonautotype.

• Fixed the issue where primary/standby switchover failed under specific circumstances.

V4.0.3

The main goal of OCP V4.0.3 is to integrate with the OBSharding platform and support taking over OBProxy services under OBSharding. You can configure and manage OBSharding-related alerting and log query services on OCP, leveraging OCP's foundational capabilities and further reducing the time cost associated with repeated configuration.

Version information

• Version: V4.0.3

• Previous version: V4.0.2

• Release date: March 03, 2023

• Supported upgrade path:

  • Currently, only direct upgrades from OCP V3.2.4 and later versions to the current version are supported.

  • For OCP V2.3.x and later, but earlier than V3.2.4, you must first upgrade to OCP V3.3.4.

  • For OCP versions earlier than V2.3.0, you must first upgrade to OCP V2.3.x, 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

• Connect to the OBSharding platform

  Note

  Only OBSharding V3.2.6 and later versions are supported, with a matching OAT version of V4.1.0 or later.

  • OCP supports creating an OBProxy cluster in OBSharding mode via API calls.

  • In OBSharding mode, an OBProxy cluster can take over OBProxy services under OBSharding.

  • For the features of the OBSharding platform, the following alert items are added based on the original OBProxy alerts:

    • 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-in failed.
    • odp_instance_expanse_failed: OBProxy instance scale-out failed.

  • The log service supports querying and downloading logs related to the OBProxy service under OBSharding.

• Password Box

  The Password Box adds a Test Credentials feature, supporting one-click validation of credential effectiveness.

• Monitoring

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

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

  • A Transaction Response Time monitoring chart is added under Transactions, including local and distributed monitoring data.

Feature Optimizations

• Optimized permissions for the platform Overview page. Only administrator users can view the platform overview information.

• Removed the OBProxy tab from the Password Box as it has no practical usage scenarios.

• Optimized the password update function. After updating the root user's password for a cluster or tenant, the system will proactively update the related credentials in the Password Box.

• Optimized error notifications when a custom installation directory is not supported for individual operating systems during cluster creation.

• Optimized the cluster upgrade function to support upgrades from OceanBase V4.0 to V4.1.

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

• Adjusted the default configurations for OCP backup alert items:

  • 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.

• Optimized the alert statistics data on the cluster overview page, supporting viewing cluster, tenant, OBServer node, and log alert statistics information for the cluster.

Fixed Issues

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 comply with relevant standards.

3. Enhanced SSH compatibility by adding support for OpenSSH 8.8 on hosts.

4. Fixed an occasional issue where the active count exceeded the all count for monitored sessions.

5. Fixed an issue where upgrading OCP from V4.0.1 to V4.0.2 might fail due to timeouts when historical data existed.

6. Fixed an issue where the system continuously triggered alerts during OCP restarts, falsely indicating a large number of hosts were offline.

7. Fixed an issue where changing an already deployed OCP deployment from non-multi-zone to multi-zone failed.

8. Fixed several other frontend display issues.

Known Issues

Version Usage Restrictions

Hardware Requirements

OCP-Server can be installed on physical servers or run in Docker containers. It supports high-availability deployment across multiple nodes.

The minimum hardware requirements for an OCP-Server node are listed in the following table.

OCP-Agent consumes minimal resources and has no specific hardware requirements for the installation node.

Operating System Requirements

The operating system requirements for installing the OCP server (including OCP-Agent) are listed in the following table.

Client Requirements

Users typically access OCP services through a web browser. The client requirements are as follows.

If you need to access OCP from a device running iOS, the version requirements are listed in the following table.

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