OCP V4.1.0

#RNDate#2023-05-26

V4.1.0 BP2

Version information

• Version: V4.1.0 BP2

• Previous version: V4.1.0 BP1

• Version release date: September 1, 2023

Bug fixes

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

• Fixed the issue where a non-root user might fail to add a host.

• Fixed the issue where the cleanup of 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 delayed by two minutes before it could be queried.

• Fixed the issue where more than two units could not be selected during expansion.

V4.1.0 BP1

Version information

• Version: V4.1.0 BP1

• Previous version: V4.1.0

• Version release date: July 20, 2023

New features

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

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

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

• Added support for O&M management of basic scenarios in OceanBase V4.2.0.0 to support POCs.

Bug fixes

• Fixed issues caused by using the 127.1 address in MetaDB across OCP clusters.

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

• Fixed the issue where backup tasks could not be rescheduled after a secondary backup was canceled.

• Fixed the error when importing hosts via the OpenAPI.

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

• Optimized the host addition process to allow successful addition even when ICMP is disabled.

• Optimized fault tolerance in primary-standby database switching scenarios to prohibit certain erroneous operations.

• Enhanced compatibility with the openEuler operating system in host management.

OCP V4.1.0

OceanBase V4.x has undergone significant changes in architecture and product form, along with a host of new features. As the companion O&M management platform for OceanBase, OCP needs to present these new features in a more user-friendly manner to reduce the learning curve for users. Additionally, as a major version release, this update further enhances the product experience, adjusts the product architecture, and improves overall capabilities.

Version information

• Version: V4.1.0

• Prerequisites: V4.0.3

• Version Release Date: May 26, 2023

• Supported upgrade path:

  • Direct upgrade from OCP V3.2.4 and later to the current version is supported.

  • For OCP V2.3.x and later versions before V3.2.4, you must upgrade to OCP V3.3.4 first.

  • For OCP versions earlier than V2.3.0, upgrade the OCP version to V2.3.x first, and then upgrade it to OCP V3.3.4.

Supported OceanBase Database versions

The following table lists the versions of OceanBase Database that are supported in OCP V4.1.0.

• 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

• Single-unit distributed integration

  Implement management of Standalone Centralized (OceanBase V4.1 and later) and Distributed Cluster in a unified manner to meet the needs of users in various scenarios.

  • You can choose between Standalone Centralized and Distributed Cluster in cluster creation. The deployment process of Standalone Centralized environments is also simplified.

  • If Standalone Centralized mode is enabled, a business tenant can be synchronously created based on the maximum available resources of the cluster when the cluster is deployed, enabling immediate business use.

  • Scale your Standalone Centralized cluster online to a Distributed Cluster cluster to meet your business growth and security requirements.

• Arbitration Service

  OceanBase Database provides arbitration services for tenants of the 2F or 4F topology when the version of the OceanBase cluster is V4.1 or later. This lowers the arbitration costs of high availability in a multi-replica topology.

  • Added the Arbitration Service Management feature, supporting deployment, start/stop, deletion, and upgrades of arbitration services.

  • Allows deploying multiple instances of the arbitration service on one node to meet the HA requirements for arbitration across different clusters.

  • The arbitration service can be added, replaced, or removed in an OceanBase cluster of V4.1 and later.

  • When arbitration service is enabled on a cluster, you can enable or disable the arbitration service for a two-node or four-node tenant.

Platform capabilities

• New information architecture

  • The primary entry point Software Package was moved under System Management and renamed to Software Package Management.

  • Added Alerts as a primary entry. Moved Alerts and Inspection from the System Management section to this location.

  • The System Management > Log Service menu entry has been upgraded to a top-level menu item.

  • The Task entry in System Management is moved to the top right corner of the Dashboard.

  • The original top-level entry Diagnosis Center is renamed to OceanBase Autonomy Service.

  • The System Management section's History Events option has been renamed to Operation Audit.

  • The System Management node contains the User Management node.

• Virtual Machine Template

  Support is provided for standardized setup of database environments for hosts added to OCP.

• Multi-Region OSS Backup

  • OSS backup for production clusters, and replicate the local backup to an OSS instance in a different region.

  • Backup scheduling, backup cycles, and retention strategies differ between two OSS instances. Local backups are retained for 30 days, while backups to the remote OSS instance are retained for 7 days.

  • A tenant of an OceanBase cluster in another region can be restored from an OSS in another region.

  • For log backup copies, synchronize the log backups first and then the log metadata to meet the timeliness requirements of log backups.

Feature enhancements

• When you set a backup strategy, you can specify the port number in the OSS endpoint.

• When you deploy an OBProxy cluster, the system checks whether the OBProxy log directory has read and write permissions.

• After a server restarts, the ocp_agent process is automatically started.

• SQL diagnostics support comparison of execution results on different hosts.

• When you create a cluster, you can enable the zone priority configuration switch. If the switch is disabled, the zone priority of the sys tenant follows the default behavior of OceanBase Database. Specifically, when the cluster version is earlier than V4.x, the first zone is prioritized; when the cluster version is V4.x or later, the zone priority is random.

• The backup storage trend interface on the overview page of global views is optimized for speed.

• The home page of the diagnostics center is optimized.

• The default value of the log backup delay alert is increased.

• OCP alerts are enhanced to support memory alerts for non-MemStore regions.

• You can customize the write lock wait failure count and average lock wait time alerts.

• The digest authentication method is supported for OCP Agent.

• The max open files parameter is added to the inspection items for the obproxy server.

• A parameter is added to control the starting OceanBase Database version for enabling cgroups.

• Monitoring queries are optimized. By using asynchronous queries, optimizing the calculation chain, and abstracting the storage layer, the peak pressure of monitoring queries is reduced, thereby improving the overall throughput of monitoring interfaces.

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

Security improvements

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

• When you deploy OCP for the first time, the system no longer provides an initial password. Instead, you need to specify a password.

• After you upload a software package, a pop-up window displays the SHA-1 value, and you need to confirm it again.

Others

The OceanBase logo has been updated.

Bug fixes

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

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

• Fixed the issue where the upgrade of OBProxy failed.

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

• Added compatibility for the display of the restore status of OceanBase Database V4.1.

• Fixed the issue where the shielding conditions created with default parameters did not take effect on the "Exceeded slow query SQL count" alert.

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

• Optimized the issue where the "Process does not exist" alert was generated when a new OBProxy cluster was created.

• Fixed the issue where a large number of error logs were generated due to timeouts in file system and disk information collection.

• Fixed the issue where the pagination was not supported when the number of pages of an OBProxy cluster exceeded 1.

• Fixed the issue where the upgrade could not be initiated when both el6 and el7 versions of OceanBase Database software packages were present.

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

• Optimized the issue where a large number of permission prompts were displayed when the overview page was inaccessible due to lack of permissions.

Known issues

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 few resources and has no special requirements for the hardware resources of the installation node.

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 web browsers. The following table lists the client requirements.

If you need to access OCP services from an iOS device, the minimum version is as follows.

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