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

• Fixed the issue where non-root users may fail to add hosts.

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

• Fixed the issue where the transaction response time in monitoring is 1000 times larger than the actual value.

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

• Fixed the issue where more than two units cannot be selected during scaling.

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, enabling multi-language switching to 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 V4.2.0.0 to facilitate POCs.

Bug fixes

• Fixed a series of issues caused by using the 127.1 address for 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.

• Enhanced fault tolerance during primary/standby database switchover and prohibited certain erroneous operations.

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

OCP V4.1.0

The architecture and product form of OceanBase V4.x have undergone significant changes, along with a wealth of new features. As the accompanying O&M management platform for OceanBase, OCP needs to present these new features in a more 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 upgrade to OCP V3.3.4 first.

  • For OCP versions earlier than V2.3.0, you must upgrade to OCP V2.3.x first, 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

• Single-node and distributed cluster management

  You can manage Standalone Centralized (available only in OceanBase Database V4.1 and later) or Distributed Cluster in the same OCP environment to meet the needs of different scenarios.

  • You can choose Standalone Centralized or Distributed Cluster when you create a cluster and simplify the deployment process for Standalone Centralized environments.

  • You can deploy Standalone Centralized environments and create a business tenant with the maximum available resources of the cluster at the same time to enable immediate business use.

  • You can online scale out Standalone Centralized environments to Distributed Cluster to meet the needs of business growth and higher security requirements.

• Arbitration Service

  You can configure the arbitration service for tenants with two or four replicas in OceanBase clusters of V4.1 and later to reduce the arbitration cost for high availability of multiple replicas.

  • The Arbitration Service Management feature is added to support the deployment, start, stop, deletion, and upgrade of 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 OceanBase clusters of V4.1 and later.

  • You can enable or disable the arbitration service for tenants with two or four replicas in a cluster that has the arbitration service enabled.

Platform features

• New information architecture

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

  • The original Alerts and Inspection under System Management are moved to the new first-level menu Monitoring and Alerts.

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

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

  • The original first-level menu Diagnosis Center is renamed to OceanBase Autonomy Service.

  • The original Operation Audit is renamed from History Events under System Management.

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

• Installation templates

  You can standardize the database environment settings for hosts added to OCP.

• Multi-region OSS backup

  • You can back up data to the local OSS of the production cluster and replicate the local backup to the OSS of a remote region.

  • 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 a tenant in a remote OceanBase cluster from the remote OSS.

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

Feature enhancements

• When setting 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 is readable and writable.

• After a server restarts, the ocp_agent process automatically starts.

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

• When you create a cluster, you can enable the zone priority configuration switch. If this switch is disabled, the zone priority of the sys tenant remains the default behavior of OceanBase Database. Specifically, if the cluster version is earlier than V4.x, the first zone is the highest priority. If 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 support memory alerts for non-MemStore regions.

• You can customize the alert items for the number of write lock wait failures and the average wait time for each lock.

• The digest authentication method is supported for OCP Agent.

• The max open files parameter is added to the inspection items for OBProxy servers.

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

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

• The Capacity Center now includes 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 the initial password instead of using the built-in default password.

• After you upload a software package, a pop-up window displays the SHA1 value. You need to confirm the value.

Other

OceanBase brand logo is updated.

Bug fixes

• Fixed the issue where the name of the standby cluster was displayed as "undefined" in cluster-level alerts for a cluster with 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 OBProxy cluster generated a "process does not exist" alert immediately after it was created.

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

• Fixed the issue where the OBProxy cluster could not navigate to the next page when it had more than one page.

• Fixed the issue where OceanBase Database could not initiate an upgrade 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 OCP-Server nodes are as follows.

OCP-Agent consumes very few resources and has no special hardware requirements for the installation node.

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

If you want to access OCP services on an iOS device, the minimum requirements are as follows.

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