OCP V4.0.0

As a product supporting OceanBase V4.0, OCP V4.0.0 not only undergoes in-depth adaptation and modification for OceanBase V4.0, but also introduces end-to-end tracing capabilities for distributed environments, providing more comprehensive link tracing and analysis.

Version information

• Version: V4.0.0

• Previous version: V3.3.4

• Release date: October 8, 2022

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

Supported OceanBase Database versions

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

• 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 end-to-end diagnostics, which have the following features:

• Established a new framework capable of performing end-to-end tracing in distributed environments.

• Provides a standard data model for transaction + SQL tracing.

• Supports end-to-end tracing from the driver through OBProxy to OBServer nodes.

Feature adaptation and changes

• For OceanBase V4.0, OCP has adapted the views and management commands for the following features:

  • Cluster management;

  • Tenant and unit management;

  • Resource management;

  • Parameter management;

  • Database management;

  • Database user management;

  • Backup and recovery;

  • SQL diagnostics;

  • SQL collection;

  • Monitoring collection;

  • Inspection;

• For OceanBase Database V4.0, OCP has undergone the following changes:

  • Added tenant-level major compaction: When OceanBase Database is V4.0 or later, cluster-level major compaction management has been changed to tenant-level management.

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

  • Database management: The Primary Zone parameter for deleting a database has been removed. When OceanBase Database is V4.0 or later, setting Primary Zone and Locality at the table, database, or table group level is no longer supported.

  • Replica view: When OceanBase Database is V4.0 or later, the concept of partition replicas has been removed.

  • Primary/standby databases: When OceanBase Database is V4.0 or later, primary/standby database-related features are not currently supported.

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

  • Secondary backup: When OceanBase Database is V4.0 or later, secondary backup functionality is not currently supported.

  • Cluster upgrade: When OceanBase Database is V4.0 or later, upgrading the cluster version is not currently supported.

Other

• cgroup is enabled by default when creating a cluster.

• Added a secondary confirmation step for max_iops when creating a unit.

Fixed issues

OCP V4.0.0 fixes the following issues:

1. Fixed an issue where log backup scheduling timeouts intermittently occurred in certain scenarios due to the thread pool being filled when SQL parsing threads were created.

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

3. Fixed the issue where task backlogs and significant memory usage increases in some cases due to ethtools execution blocking.

4. Fixed the issue where some tasks fail during concurrent reinstallation of agents for a large number (100+) of machines.

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

6. Fixed the issue where an exception is reported when creating a standby cluster without a zone for the server in multi-cluster mode.

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

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

9. Fixed the issue where alerts do not take effect when subscribing to both OBProxy and other application alerts simultaneously.

10. Fixed the issue where inaccurate and misleading inode usage monitoring alerts are triggered.

11. Fixed the issue where disk read-only status is incorrectly reported as an alert.

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

13. The SQL diagnostics page has removed the ineffective Server filtering feature.

Known issues

Version usage limitations

Hardware requirements

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

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

OCP-Agent consumes very few resources and does not have 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. Therefore, the client requirements are as follows.

The following table lists the minimum requirements for iOS devices to access OCP.

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