OCP V4.1.0

V4.1.0 BP2

Version information

• Version: V4.1.0 BP2

• Previous version: V4.1.0 BP1

• Release date: September 01, 2023

Bug fixes

• Fixed the issue where the displayed tenant CPU usage was 100 times higher than the actual value.

• Fixed the issue where adding a host by a non-root user might fail.

• Fixed the issue where cleaning up useless alert history failed.

• Fixed the issue where the displayed transaction response time in monitoring was 1,000 times higher than the actual value.

• Fixed the issue where some real-time monitoring data was available only two minutes after the query.

• Fixed the issue where more than 2 units could not be selected during scale-out.

V4.1.0 BP1

Version information

• Version: V4.1.0 BP1

• Previous version: V4.1.0

• Release date: July 20, 2023

New features

• Added support for two common single sign-on (SSO) authentication and authorization methods: OAuth2 and CAS.

• Optimized English terms and text within the product to enable multi-language switching, meeting internationalization requirements.

• Optimized the startup logic of OBAgent to support automatic cleanup of historical PID files.

• Added support for operational management and control of basic scenarios in OceanBase Database V4.2.0.0, aiding in proof-of-concept (POC) efforts.

Bug fixes

• Fixed a series of cross-OCP cluster issues caused by using the 127.1 address for MetaDB.

• Fixed the issue where topology diagrams had no monitoring data.

• Fixed the issue where a backup task could not be rescheduled after being canceled for the second time.

• Fixed the issue where an error was reported when importing hosts using the OpenAPI.

• Optimized the issue where adding a host failed in specific shell environments.

• Optimized the host addition process so that it could succeed even when ICMP keep-alive was disabled.

• Improved fault tolerance in primary/standby database switchover scenarios by prohibiting certain incorrect operations.

• Added compatibility for the openEuler system in host management.

OCP V4.1.0

The architecture and product form of OceanBase Database V4.x have undergone significant changes, bringing numerous new features. As the supporting O&M management platform for OceanBase Database, OCP needs to present these new features to users in a simpler and more user-friendly way, reducing the learning curve. Additionally, this major version further optimizes the product experience, adjusts the architecture, and enhances capabilities.

Version information

• Version: V4.1.0

• Previous version: V4.0.3

• Release date: May 26, 2023

• Supported upgrade path:

  • Currently, only direct upgrades from OCP V3.2.4 and later 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.1.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

OceanBase V4.x

• Unified management of single-node and distributed clusters

  Enables simultaneous management of Standalone Centralized (only available in OceanBase V4.1 and later) or Distributed Cluster OceanBase environments, meeting diverse user requirements.

  • Supports selecting Standalone Centralized or Distributed Cluster mode during cluster creation, and simplifies the deployment process for Standalone Centralized environments.

  • Supports creating a business tenant with the maximum available resources of a cluster when deploying Standalone Centralized, enabling immediate business use.

  • Supports online scaling from Standalone Centralized to Distributed Cluster to meet business growth and higher security requirements.

• Arbitration Services

  Supports configuring the arbitration service for tenants with two or four full-featured replicas in OceanBase clusters of version V4.1 and later, thereby reducing the arbitration cost for high availability in multi-replica setups.

  • Added the Arbitration Service Management feature, enabling capabilities such as deployment, start/stop, deletion, and upgrade of arbitration services.

  • Supports deploying multiple arbitration service instances on a single node to meet the arbitration and high availability requirements of different clusters.

  • Supports adding, replacing, and removing arbitration services in OceanBase clusters of version V4.1 and later.

  • Supports enabling or disabling the arbitration service for tenants with two or four full-featured replicas after an arbitration service has been added to the cluster.

Platform features

• New information architecture

  • The original top-level entry Software Package has been moved under Administration and renamed Packages.

  • Added a new top-level entry Monitoring & Alerts, moving the original Alerts and Inspections from Administration to this path.

  • The original Administration entry Log Services has been promoted to a top-level entry.

  • The original Task entry under Administration has been moved to the upper-right corner of the Home page.

  • The original top-level entry Diagnostic Center has been renamed Diagnosis.

  • The original Historical Events under Administration has been renamed Audit.

  • The original Security under Administration has been renamed User Management.

• Deployment templates

  For hosts added to OCP, standardized settings can be configured for the database environment.

• Multi-OSS geographically distributed backup

  • Local OSS backup in the production cluster, while replicating local backups to remote OSS.

  • Different backup scheduling, cycles, and retention policies for the two-region OSS: 30 days of backup retained locally, 7 days retained remotely.

  • Tenant recovery in a remote OceanBase cluster can be performed using remote OSS.

  • When replicating log backups, log metadata is synchronized first, followed by the log backup data, to meet timeliness requirements for log backup.

Feature enhancements

• When setting a backup strategy, you can now enter the port number in the OSS access domain name.

• Added a check for read/write permissions on the OBProxy log directory during OBProxy cluster deployment.

• The ocp_agent process is automatically restarted after a server reboot.

• SQL diagnostics now support execution comparison across different hosts.

• When creating a cluster, a new zone priority configuration switch is added. When this switch is off, the zone priority for the sys tenant follows OceanBase's default behavior: for cluster versions earlier than V4.x, the first zone has the highest priority; for V4.x and later, it is random.

• The speed of the backup storage trend interface on the global view overview page has been optimized.

• The display on the homepage of the diagnostics center has been optimized.

• The default threshold for log backup latency alerts has been increased.

• OCP alert items have added memory alerts for non-MemStore regions.

• Support for custom addition of write lock wait failure count and average wait time per lock alert items.

• OCP Agent has added digest authentication.

• Added an inspection item for max open files on OBProxy servers.

• Added a parameter to control the starting OceanBase Database version for enabling cgroup.

• Monitoring query optimization: By using asynchronous queries, optimizing the query computation chain code, and abstracting the storage layer, peak monitoring query pressure is reduced, thereby improving the overall throughput of the monitoring interface.

• The Capacity Center has added Capacity Risks and the tenant Capacity Usage Overview.

Security improvements

• Sensitive information involved in web page access interface interactions is transmitted via encrypted channels.

• For new OCP deployments, a built-in initial password is removed and replaced with a user-specified password.

• After uploading a software package, a pop-up window displays the SHA1 value, requiring user confirmation.

Other

The OceanBase brand logo has been updated.

Bug fixes

• Fixed the issue where the standby cluster name is displayed as "undefined" in cluster-level alerts for clusters with standby clusters.

• Fixed the issue where disk statistics for tenant resource management are sometimes inaccurate.

• Fixed the issue where upgrading the OBProxy version fails.

• Fixed the issue where the "exporter does not exist" false alert is still generated after resources are deleted.

• Added compatibility for displaying the recovery status of OceanBase V4.1.

• Fixed the issue where the silence rule created with default parameters does not take effect for the "Excessive Slow Query SQL Count" alert.

• Fixed the issue where OCP users can view monitoring and alert data without permission.

• Optimized the issue where the "process does not exist" alert is reported when an OBProxy cluster is newly created.

• Fixed the issue where excessive error logs are generated by the agent due to timeouts in file system and disk information collection.

• Fixed the issue where pagination fails for OBProxy clusters with more than 1 page.

• Fixed the issue where the inability to initiate an upgrade for OceanBase occurs when both EL6 and EL7 versions of the same OceanBase package are present.

• Optimized the OCP image by adding commonly used Python class libraries.

• Optimized the issue where a large number of permission prompts are displayed when accessing the overview page without permission.

Known issues

Version usage restrictions

Hardware requirements

OCP-Server can be installed on physical servers or run in Docker containers. OCP-Server supports multi-node high-availability deployment.

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

OCP-Agent consumes very few resources and has no specific hardware requirement 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 × 810.