OceanBase Database Proxy Enterprise Edition V4.4.0

V4.4.0

Version information

• Release date: June 1, 2026

• Version: V4.4.0

• RPM version: obproxy-4.4.0.0-382026052716

Version overview

ODP V4.4.0 is the latest version in the ODP 4.x series. It focuses on enhancing routing capabilities and security authentication. In terms of SQL proxy, the routing strategy for temporary table scenarios is optimized so that requests are no longer forcibly routed to the same OBServer node after a client session accesses a temporary table, thereby improving routing accuracy. It also adds support for the max_execution_time system variable, enabling timeout control for single read-only SELECT statements and improving compatibility with MySQL 8.0. At the same time, it supports the caching_sha2_password authentication method, which stores password hashes based on the SHA-256 algorithm to further improve authentication security. In terms of RPC proxy, ODP V4.4.0 introduces OBKV weak-read routing, which can route read requests to Follower replicas in the same IDC to reduce cross-region access latency and meet the needs of users who require nearby IDC reads.

This version is recommended for both cloud and on-premises businesses for POC testing and production.

Key feature descriptions

SQL proxy

• Temporary table routing optimization

  When a client connects to an OBServer through ODP, a client session may establish sessions with multiple OBServers on the backend. These sessions share temporary table data, and if any session disconnects, the related temporary table data is automatically cleaned up. However, this brings a problem: if a session on a certain OBServer disconnects but the connection between ODP and the client remains, the client may think the temporary table still exists and continue to access it, leading to data correctness issues. To ensure the consistency of temporary table data, in earlier versions, after a client session accessed a temporary table, ODP would forcibly route all subsequent requests of that session to the same OBServer node. However, this prevented non-temporary-table requests from being accurately routed, affecting performance.

  ODP V4.4.0 optimizes the temporary table routing strategy: it no longer forcibly routes all requests to the node where the temporary table is located, but instead parses the SQL normally and routes accurately. At the same time, ODP treats the OBServer session that created the temporary table as the primary session. When that session disconnects abnormally, the corresponding client session is also disconnected, ensuring the correctness of temporary table data.

• Support for the max_execution_time variable

  ODP V4.4.0 adds support for the max_execution_time system variable. MySQL 8.0 introduced this variable to control the execution timeout of a single read-only SELECT statement. The new version of ODP supports this variable for timeout control of single read-only SELECT statements, further improving compatibility with MySQL 8.0.

• Support for the caching_sha2_password authentication method

  Currently, ODP supports the mysql_native_password authentication method, which is based on the SHA1 hash algorithm and has certain security risks. ODP V4.4.0 adds support for the caching_sha2_password authentication plugin. This plugin stores password hashes based on the SHA-256 algorithm and performs authentication through a challenge-response mechanism. Even if the passwords are the same, the stored results are different, providing higher security and meeting users' higher requirements for password authentication security.

• Support for synonym routing with global indexes

  ODP V4.4.0 improves synonym routing capabilities and supports accurate routing of synonyms with global indexes.

RPC proxy

• OBKV weak-read routing

  In OceanBase cross-region disaster recovery deployments, Leader replicas are usually distributed across Zones in different cities. Previously, OBKV did not support weak reads, so read requests might be routed to Leader nodes in remote cities, resulting in high cross-region network latency and making it difficult to meet the needs of businesses sensitive to read latency, such as risk control.

  ODP V4.4.0 introduces OBKV weak-read routing. ODP determines whether a request is a weak-read request based on the read consistency level in the request, and uses the newly added rpc_proxy_route_policy configuration item to specify the routing policy (FOLLOWER_FIRST or FOLLOWER_ONLY, default is FOLLOWER_FIRST). Weak-read requests are preferentially routed to FOLLOWER replicas in the same IDC to reduce cross-region access latency.

Compatibility changes

Configuration item changes

Behavior changes

Supported OBServer versions

OBServer 4.x, OBServer 3.x, and earlier versions are supported.

Recommended versions

ODP 4.4.0 supports many new features and has been enhanced for stability. It is recommended for users who depend on the new features.

Bug fixes

• Fixed the issue where PL cache was not refreshed, causing the old cache to be reused.

• Fixed the issue where the GV$SYSSTAT HBase batch delete operation count was counted incorrectly.

• Fixed the issue where the ODP log timestamp was inconsistent with the system time.

• Fixed the issue where port 3307 connection failed for AWS standalone Kubernetes ODP.

• Fixed the issue where the vip field in the odp_new_client_connections metric exposed by ODP contained garbled characters, causing Agent parsing failures.

• Fixed the ODP startup failure caused by the number of shard_scan_all and obkv_task_threads threads being 0 when the machine CPU parameter was set to 1.

• Fixed the routing inaccuracy issue caused by parsing failures when the SQL contained WHERE clauses with specific structures.