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 as a non-root user might fail.

• Fixed the issue where cleaning up unused 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.

• Supports operational management and control for basic scenarios of OceanBase Database V4.2.0.0, aiding in proof-of-concept.

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.

• Fixed the issue where an error occurred when importing hosts via the OpenAPI interface.

• 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 keepalive was disabled.

• Improved fault tolerance in primary/standby switchover scenarios and prohibited certain incorrect operations.

• Added compatibility for openEuler systems in host management.

OCP V4.1.0

The architecture and product form of OceanBase V4.x have undergone significant changes, introducing many new features. As the supporting O&M management platform for OceanBase, OCP needs to present these new features to users in a simpler and more user-friendly way, reducing the difficulty of use. Additionally, as a major version update for OCP, this release further optimizes the product experience, adjusts the product architecture, and enhances product 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 versions to the current version are supported.

  • For OCP V2.3.x and later, but before 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 standalone and distributed environments

  Enables simultaneous management of standalone centralized (only available in OceanBase V4.1 and later) or distributed clusters, meeting user requirements in different scenarios.

  • Supports selecting standalone centralized or distributed cluster mode when creating a cluster, and simplifies the deployment process for standalone centralized environments.

  • Supports simultaneously creating a business tenant with the maximum available cluster resources during standalone centralized deployment, enabling immediate business use.

  • Supports online scaling from a standalone centralized environment to a distributed cluster to meet business growth and higher security requirements.

• Arbitration service

  Supports configuring an arbitration service for 2F or 4F tenants in OceanBase clusters of version V4.1 and later, 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 2F or 4F tenants after an arbitration service has been added to a cluster.

Platform features

• New information architecture

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

  • Added a new top-level entry Monitoring & Alerts, moving the original Alerts and Inspection entries under System Management to this path.

  • The original Log Service under System Management has been promoted to a top-level entry.

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

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

  • The original Historical Events under System Management has been renamed Operation Audit.

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

• Deployment templates

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

• Multi-region OSS backup

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

  • The backup scheduling, cycle, and retention policies differ between the two regions. 30 days of backups are retained locally, and 7 days are retained remotely.

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

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

Feature enhancements

• When setting a backup strategy, you can now enter a 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 machine 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 below V4.x, the first Zone has priority; for cluster versions V4.x and above, it is random priority.

• Optimized the interface speed for the backup storage trend on the global view overview page.

• Optimized the display on the homepage of the Diagnostics Center.

• Increased the default value for log backup latency alerts.

• Added memory alerts for non-MemStore areas to OCP alert items.

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

• Added digest authentication for OCP Agent.

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

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

• Monitoring query optimization: reduces peak monitoring query pressure through asynchronous queries, optimized query computation link code, and abstracted storage layers, thereby improving the overall throughput of the monitoring interface.

• Capacity Center now includes Capacity Risk and Tenant Total Capacity Usage Overview.

Security improvements

• Sensitive information involved in web page access interface interactions is encrypted during transmission.

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

• After the software package is uploaded, a pop-up window displays the SHA1 value, which requires user confirmation.

Other

The OceanBase brand logo has been updated.

Bug fixes

• Fixed the issue where the standby cluster name was displayed as "undefined" in cluster-level alerts when a standby cluster existed.

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

• Fixed the issue where upgrading the OBProxy version failed.

• Fixed the issue where the "exporter does not exist" false alert continued to occur after resources were deleted.

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

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

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

• Optimized the issue where an "Process Does Not Exist" alert was triggered immediately upon creating an OBProxy cluster.

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

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

• Fixed the issue where the presence of both EL6 and EL7 versions of the OceanBase package prevented OceanBase from initiating an upgrade.

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

• Optimized the issue where accessing the overview page without permission triggered multiple permission prompts.

Known issues

Version usage restrictions

Hardware requirements

OCP-Server can be installed on physical servers or run in Docker containers. OCP-Server 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 very few resources and has no specific hardware requirements for the installation node.

Operating system requirements

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

Client requirements

Typically, users 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.