OCP V4.0.0

#RNDate#2022-10-08

OCP V4.0.0 is a product that is closely integrated with OceanBase Database V4.0. It is deeply adapted and modified for OceanBase Database V4.0 and provides full-link tracing capabilities in a distributed environment. It has more comprehensive link tracing and analysis capabilities.

Version information

• Version: V4.0.0

• Previous version: V3.3.4

• Version release date: October 8, 2022

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

Supported OceanBase Database versions

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

OCP V4.0.0 introduces the full-link diagnostics feature, which has the following characteristics:

• A new framework is established to support full-link tracing in a distributed environment.

• The transaction + SQL tracing standard data model is provided.

• Full-link tracing is supported from the driver to OBProxy and then to the OBServer node.

Feature adaptation and changes

• For OceanBase V4.0, OCP adapts the views and management commands of the following features:

  • Cluster management;

  • Tenant and unit management;

  • Resource management;

  • Parameter management;

  • Database management;

  • Database user management;

  • Backup and restore;

  • SQL diagnostics;

  • SQL collection;

  • Monitoring collection;

  • Inspection;

• For OceanBase V4.0, OCP changes the following features:

  • Tenant merge: When OceanBase is V4.0 or later, cluster-level tenant merge is changed to tenant-level tenant merge.

  • Unit management: When OceanBase is V4.0 or later, only tenant-level overall scaling is supported, and zone-level scaling is no longer supported.

  • Database management: The Primary Zone parameter is removed from the database. When OceanBase is V4.0 or later, table-level, database-level, and table group-level settings for Primary Zone and Locality are no longer supported.

  • Replica view: When OceanBase is V4.0 or later, the concept of partition replica is removed.

  • Primary and standby databases: When OceanBase is V4.0 or later, the related features of primary and standby databases are temporarily not supported.

  • Tenant backup and tenant snapshot backup: When OceanBase is V4.0 or later, the tenant backup and tenant snapshot backup features are temporarily not supported.

  • Secondary backup: When OceanBase is V4.0 or later, the secondary backup feature is temporarily not supported.

  • Cluster upgrade: When OceanBase is V4.0 or later, the cluster version upgrade feature is temporarily not supported.

Other information

• cgroup is enabled by default when you create a cluster.

• When you create a unit, you are prompted to confirm the max_iops value.

Fixed issues

OCP V4.0.0 fixes the following issues:

1. Fixed the issue where SQL parsing threads can occupy the thread pool, leading to intermittent log backup scheduling timeouts in certain scenarios.

2. Fixed the issue where the database name is not displayed on the SQL details page when you enter it from a non-SQL list page.

3. Fixed the issue where task accumulation and significant memory increases occur due to ethtools execution blocking in certain scenarios.

4. Fixed the issue where some tasks fail when you reinstall the Agent of a large number (100+) of servers concurrently.

5. Enhanced the security of password display in OSS backup logs.

6. Fixed the issue where an exception is reported when you create a standby cluster without a Server in a zone in multi-cluster mode.

7. Fixed the issue where QPS monitoring before the upgrade cannot be queried after upgrading from V3.1.x to V3.2.x.

8. Fixed the issue where alerts are inaccurate due to unreleased MemTables.

9. Fixed the issue where alerts do not take effect when you subscribe to OBProxy and other application alerts concurrently.

10. Fixed the issue where inode usage monitoring is inaccurate and false alarms are generated.

11. Fixed the issue where disk read-only false alarms are generated.

12. Fixed the issue where TCP retransmission rate monitoring occasionally exceeds 100%.

13. Removed the invalid filter by server on the SQL diagnostics page.

Known issues

Version 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 an OCP-Server node are as follows:

OCP-Agent consumes very little resources and has no special hardware requirements.

Operating system requirements

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

Client requirements

General users access OCP services through a web browser. The following table lists the client requirements.

If you want to access OCP services from an iOS device, the minimum operating system version is as follows:

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