OCP V4.1.0

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 is 100 times larger than the actual value.

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

• Fixed the issue where the cleanup of useless alert history fails.

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

• Fixed the issue where some real-time monitoring data is delayed by two minutes before it can be queried.

• Fixed the issue where you cannot select more than 2 units when you scale out the cluster.

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 two common single sign-on (SSO) authentication and authorization methods: OAuth2 and CAS.

• Optimized English terms and text in the product to support multi-language switching and meet internationalization requirements.

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

• Added support for O&M control of basic scenarios in OceanBase Database 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 map had no monitoring data.

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

• Fixed the error reported by the import host interface of 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 the primary/standby database switching scenario to prohibit some 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 numerous new features. As the companion O&M management platform for OceanBase, OCP needs to present these new features in a more simple and user-friendly manner to reduce the difficulty for users. Additionally, as a major version of 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

• Version release date: May 26, 2023

• Supported upgrade path:

  • You can directly upgrade from OCP V3.2.4 to the current version.

  • For OCP V2.3.x and earlier versions, 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, and 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

• Integrated single-node and distributed deployment

  You can manage both Standalone Centralized (available in OceanBase Database V4.1 and later) and Distributed Cluster in a unified environment, meeting diverse user needs.

  • When you create a cluster, you can choose between Standalone Centralized and Distributed Cluster modes. The deployment process for Standalone Centralized environments is streamlined.

  • When you deploy a Standalone Centralized cluster, you can automatically create a business tenant using the maximum available resources of the cluster, enabling immediate business use.

  • You can online scale out a Standalone Centralized cluster to a Distributed Cluster, meeting growing business needs and higher security requirements.

• Arbitration Service

  If an OceanBase cluster is V4.1 or later, you can configure the arbitration service for 2F or 4F tenants to reduce the arbitration cost for high availability in multi-replica environments.

  • The Arbitration Service Management feature is introduced, allowing you to deploy, start, stop, delete, and upgrade the arbitration service.

  • You can deploy multiple arbitration service instances on a single node to meet the high availability requirements of different clusters.

  • You can add, replace, or remove the arbitration service in an OceanBase cluster of V4.1 or later.

  • After you add the arbitration service to a cluster, you can enable or disable the arbitration service for 2F or 4F tenants.

Platform features

• New information architecture

  • The original first-level entry Software Package is moved to System Management and renamed to Software Package Management.

  • A new first-level entry Monitoring and Alerts is introduced. The original Alerts and Inspection entries under System Management are moved to this entry.

  • The original Log Service entry under System Management is promoted to a first-level entry.

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

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

  • The original Operation Audit entry is renamed from History Events.

  • The original Security entry under System Management is renamed to User Management.

• Installation templates

  For hosts added to OCP, you can standardize the database environment settings.

• Multi-region OSS backup

  • Local OSS backup is performed for the production cluster, and the local backup is replicated to the remote OSS.

  • The backup scheduling, backup cycle, and retention strategy are different for the local and remote OSS. The local backup is retained for 30 days, and the remote backup is retained for 7 days.

  • You can restore tenants in the remote OceanBase cluster by using the remote OSS.

  • When you replicate log backups, you can synchronize the log backups and log metadata to meet the timeliness requirements of log backups.

Feature enhancements

• When you set a backup strategy, you can specify a 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 is restarted, the ocp_agent process is automatically started.

• SQL diagnostics support cross-host comparison.

• 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 has the highest priority. 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 diagnostic center is optimized.

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

• OCP alerts support memory alerts in non-memstore zones.

• You can customize alerts for write lock wait failures and average lock wait time.

• OCP Agent supports digest authentication.

• The inspection item of max open files is added to the OBProxy server.

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

• The monitoring query is optimized. By using asynchronous queries, optimizing the computing chain code, and abstracting the storage layer, the peak pressure of monitoring queries is reduced, thereby improving the overall throughput of monitoring interfaces.

• Capacity Center supports Capacity Risks and tenant Capacity Usage Overview.

Security enhancements

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

• When you deploy OCP for the first time, you can specify a password instead of using the built-in initial password.

• After you upload a software package, a dialog box pops up to prompt you to enter the SHA1 value. You need to confirm the value.

Others

The OceanBase logo has been updated.

Bug fixes

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

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

• Fixed the issue where upgrading the OBProxy version failed.

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

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

• Fixed the issue where the shielding condition created with default parameters did not take effect for the "slow query SQL count exceeded" alert.

• Fixed the issue where an OCP user without the required permissions could still view monitoring and alert data.

• Optimized the issue where an "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 pagination was not supported for OBProxy clusters with more than one page.

• Fixed the issue where the upgrade could not be initiated when both el6 and el7 versions of OceanBase 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 could not be accessed due to insufficient permissions.

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 few resources and does not have specific hardware requirements.

Operating system requirements

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

Client requirements

General users access OCP services through a web browser. Therefore, the following client requirements apply.

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

For the best user experience, we recommend using a display with a resolution of 1440 x 810 or higher.