OCP V4.2.1

V4.2.1 BP1

Version information

• Version: V4.2.1 BP1

• Previous version: V4.2.1

• Release date: December 08, 2023

Bug fixes

• Fixed the performance issue where resources of the sys tenant were excessively consumed when the data volume was large.

• Fixed the issue where the frontend page became unresponsive when clicking any time component.

• Fixed the dependency on the MySQL client when deploying a standalone centralized cluster.

• Optimized the retrieval speed of Alerts information on the Backup & Restore page in the cluster console.

• Optimized the overall performance of OCP. Reduced the CPU and memory resource consumption required by OCP and significantly improved the response speed of web pages.

V4.2.1

OCP V4.2.1 officially supports OceanBase V4.2.1. It enables monitoring and alerting for end-to-end components of OceanBase Database, including support for custom monitoring, enhanced support for tenant- and session-level end-to-end tracing, and added monitoring and alerting capabilities for OBLB and OBDNS. Additionally, this version introduces 17 optimizations in cluster management, tenant management, monitoring and alerting, and task management, focusing on improving product usability to create a simpler and more user-friendly database management platform.

Version information

• Version: V4.2.1

• Previous version: V4.2.0

• Release date: November 21, 2023

• Supported upgrade path:

  • Currently, only upgrades from OCP V3.2.4 and later versions to the current version 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.2.0 supports the following versions of OceanBase Database:

• OceanBase V1.4.x

• OceanBase V2.1.x

• OceanBase V2.2.x

• OceanBase V3.1.x

• OceanBase V3.2.x

• OceanBase V4.x

New product features

OceanBase V4.x adaptation

• Supports end-to-end diagnostic capabilities at the tenant and session levels, helping users analyze transaction-level execution times from three perspectives: client > OBProxy > OceanBase cluster. This enables rapid root cause identification and timely fault resolution. This feature requires deploying the OpenSearch service and imposes version constraints on all components along the entire chain. For details, see Query the chain.

• Adapts to the __all_virtual_dump_tenant_info view to monitor and alert on tenant queue usage.

• Adapts to the semantics of the tenant parameter tenant=all, which applies only to user tenants and does not take effect for the sys or Meta tenant.

• Adapts to changes in the RS job view, adding task types such as ALTER_TENANT_PRIMARY_ZONE, ALTER_TENANT_LOCALITY, and ALTER_RESOURCE_TENANT_UNIT_NUM.

• Supports displaying OceanBase log disk usage information.

Feature enhancements

• OBProxy management

  • Supports hot restart of OBProxy versions V3.2.8 and later, resolving the issue where maintenance or upgrade operations affecting online services could lead to service interruptions.

  • Supports operational tasks for OBProxy clusters, including enabling, restarting, and stopping the cluster, as well as batch starting, batch restarting (including hot restart), and batch stopping of OBProxy nodes. This enhances OBProxy management capabilities and improves user operational efficiency.

• Monitoring and Alerts

  • Supports custom monitoring capabilities. By defining collection items and monitoring items, and associating them with monitoring charts and alerts, users can create customized monitoring and alerting solutions. This addresses scenarios where OCP's built-in alerts cannot meet business requirements (currently only supporting alerts for related metrics within the sys tenant).

  • Supports alert capabilities for OBLB & OBDNS, providing a total of 16 alert metrics such as process status and process connectivity, thereby realizing alert capabilities across the entire OceanBase architecture.

  • Supports monitoring the percentage of active Memstores. The view path is Tenant > Performance Monitoring > Performance and SQL > MEMStore Usage Percentage.

  • Supports monitoring the number of minor compactions per tenant, helping users prevent business impact caused by triggering a cluster-level major compaction when the number of minor compactions per tenant in OceanBase V3.X exceeds the threshold.

  • Supports an alert when the total space usage of the OceanBase recycle bin exceeds 100 GiB, reducing the impact on customer business due to excessive partitions in the OceanBase V3.X recycle bin or untimely cleanup.

  • Supports alerts for OCP agent version inconsistencies with the OCP version, avoiding abnormal behavior during subsequent operations and enhancing system stability.

• Inspection

  • Supports inter-server connectivity detection, including SQL ports and RPC ports, assisting users in quickly locating business interruptions caused by network or host failures.

  • Supports checking the usage rate of OceanBase macroblocks, helping users identify the actual data volume and disk usage of tenants and tables, and then reduce disk fragmentation through major compaction operations.

Feature Optimizations

• For objects such as clusters, tenants, and OBProxy, and for hosts that are unavailable or offline, supports analysis of the cause of the exception, providing error information, error causes, and solutions to help users resolve faults and ensure stable business operation.

• Cluster Management:

  • Supports specifying startup parameters, such as memory_limit and system_memory, when adding or replacing an OBServer. This resolves issues like expansion failure and resource waste when hardware resources of machines within the cluster are inconsistent.

  • Supports specifying startup parameters, such as cpu_count and devname, when creating an arbitration service.

  • Added support for providing the option to perform a Memstore minor compaction during cluster restart, zone restart, OBServer restart, or OBServer process stop. This primarily addresses the issue of slow OBServer recovery without having performed a minor compaction.

  • Supports verifying the paths and sizes of the cluster log disk and data disk, such as detecting log disk size and whether the data disk and log disk are deployed on the same physical disk, and provides corresponding prompts. This avoids subsequent database runtime exceptions and enhances system stability.

  • Added a prompt for deadlock detection: This feature is not recommended for production systems running OceanBase V3.X.

  • Provides detection for support of Large System Extensions (LSE) instructions lower than ARM8.1, preventing deployment failures in OceanBase clusters.

• Host Management:

  • Supports associating a host IP with its corresponding OceanBase cluster or OBProxy cluster, and supports quick navigation to the respective cluster.

  • Supports quick navigation to the corresponding task for hosts in an operational state (task types include deleting a host and Reinstall OCP Agent).

• Monitoring and Alert Management:

  • Distinguishes between active alerts, historical alerts, and adds a display reminder for active alerts in the status bar, enhancing users' attention to current active alerts.

  • Added alert category options under Alerts > Alert Events, helping users quickly identify alert types and improving product usability.

  • Alert information (such as cluster alerts, tenant alerts, OBServer alerts) now provides the affected host IP or tenant name, helping users quickly identify the scope of fault impact.

  • The cluster name has been changed to Cluster Name:Cluster ID, and a primary/secondary marker has been added for clusters.

• Backup and Recovery Management:

  The cluster name has been changed to Cluster Name:Cluster ID, and a primary/secondary marker has been added for clusters.

• Log Search Management:

  In Trace Query > Search, new conditions such as sql_trace_id, trans_id, sess_id, and client_info have been added to help associate user links, thereby effectively improving query efficiency.

• Task Management:

  • Supports displaying exception information for failed tasks and locating it to the first error log position, helping users efficiently pinpoint the cause of faults.

  • Supports batch retrying of failed tasks. For scenarios with a large number of failures, such as Restart or ReInstall OCP Agent, this can significantly improve user O&M efficiency.

  • Supports quickly associating objects under maintenance, such as clusters, tenants, OBProxies, and hosts, with tasks. This facilitates users in quickly checking task status for subsequent O&M operations.

Product Behavior Changes

• Cluster Management: Deadlock Analysis has been changed to View Deadlock History Information.

• Tenant Management: The display of non-compliant usernames is no longer supported in Tenant (MySQL) > User Management > Users.

• Monitoring and Alert Management: The ability to upload configuration files has been removed from Alert Channel > Channel Type (Custom Script), to avoid issues with such file loss during upgrade scenarios.

Key features

End-to-end diagnostics at the tenant and session levels

OceanBase is a distributed database with extremely complex front-end and back-end call chains. When business issues such as timeouts or performance anomalies occur, users often cannot determine whether the problem lies with internal OceanBase components or network issues. They can only analyze based on experience and OBServer logs, which leads to lengthy analysis and resolution times, affecting business stability. Therefore, OCP provides an end-to-end diagnostics mechanism to monitor the time consumed across the entire chain from Client > OBProxy > OBServer, helping users quickly identify the root cause of problems.

If you need to view related log information in OCP, first configure parameters for the data mid-end module, link query collection, and OpenSearch (ES). If you only need to enable this for specific tenants or sessions, disable the end-to-end diagnostics feature for other tenants. Then, go to Log Services > Trace Query and filter by time, tenant, search content (such as sql_id, trans_id, sess_id, etc.), and link time. Current end-to-end diagnostics tracking is dimensioned by database transactions, collecting data such as link time, driver time, OBProxy time, and OB time. Through simple timing analysis, you can identify the main issue points and go to the corresponding trace to view specific times (Spans/Tags), thereby quickly locating the real problem.

Custom monitoring

Custom monitoring allows users to create custom monitoring charts and alerts that fit their business scenarios when OCP's built-in monitoring does not meet needs. This helps users promptly perceive internal system changes and make timely, quick decisions. The entire feature module is divided into three tabs: Collection Items, Metrics, and Charts. Specifically:

1. Collection Items represent raw monitoring data collected from different data sources. The system currently has over 50 built-in collection items.

2. Metrics represent calculated metrics generated based on collection items, such as maximum, minimum, or average values, using dozens of algorithms. You can choose or create custom expressions based on your usage of monitoring data. The system currently has over 200 built-in monitoring items.

3. Charts can consist of one or more metrics and support selecting a chart placement location and previewing the chart. Users can also implement alert capabilities for corresponding metrics through the custom alert feature.

Fixed issues

OCP V4.2.1 primarily fixes the following issues:

• Fixed the issue where non-admin users in OCP could not access alert details.
• Fixed the issue where a rollback of an OBProxy creation task was incomplete, leading to failure upon redeploying OBProxy.
• Fixed the issue where the tenant variable max_allowed_packet could not be modified on the OCP side.
• Fixed the issue where the number of tenant sessions was counted incorrectly.
• Optimized the upgrade speed from OCP V3.3.x to V4.2.x, which slowed down when there was a large amount of monitoring data.
• Optimized the volume of collected data, improving collection performance and stability.
• Optimized the timeout logic for O&M SQL queries, now supporting settings and performing more stably.
• Optimized monagent logs to avoid generating excessive useless debug logs.

Optimized the alert behavior when MetaDB is unavailable.

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 with 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 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.