ODP Enterprise Edition V4.2.1

V4.2.1 BP2 hotfix5

Version information

• Release date: March 11, 2025

• Version: V4.2.1 BP2 hotfix5

• RPM version: obproxy-4.2.1.0-72025031114

Bug fixes

Fixed the issue where an INSERT request initiated to a partitioned table is routed to a non-leader node in OceanBase Database V1.4.x.

V4.2.1 BP2 hotfix4

Version information

• Release date: June 04, 2024

• Version: V4.2.1 BP2 hotfix4

• RPM version: obproxy-4.2.1.0-20240604114727

Bug fixes

• Fixed the issue where startup parameters specified by the -o option may be lost upon initial startup.
• Fixed the issue where the statistics collected in Prometheus monitoring are smaller than actual values.
• Fixed the issue where garbled characters exist in output strings of Prometheus.
• Fixed the issue of inaccurate routing in scenarios where enable_cached_server is set to True, if proxy_idc_name is not obtained upon login.
• Fixed the issue where OceanBase Database Proxy (ODP) hangs due to multi-level binlog configurations, causing connections to time out and terminate.
• Fixed the issue where Prometheus outputs incorrect database names.

V4.2.1 BP2 hotfix3

Version information

• Release date: February 22, 2024

• Version: V4.2.1 BP2 hotfix3

• RPM version: obproxy-4.2.1.0-20240229214253

Bug fixes

• Fixed the issue where an OceanBase cluster cannot be connected from Visual Studio for Windows.
• Fixed the issue where an SSL connection cannot be established by the C# driver with the database.

V4.2.1 BP2 hotfix2

Version information

• Release date: December 20, 2023

• Version: V4.2.1 BP2 hotfix2

• RPM version: obproxy-4.2.1.0-20231220145047

Overview

Address-level binlog configurations are supported.

Bug fixes

• Fixed the issue where a core dump is generated for ODP in a scenario where the prepared statement (PS) protocol is enabled in an Advanced RISC Machine (Arm) environment.
• Fixed the issue where memory leaks occur when the memory usage of ODP increases slowly, causing a force restart.
• Fixed the issue where the performance of queries based on the specified cursor fetch size is poor when ODP connects to an OceanBase cluster.
• Fixed the issue where, when the number of connections exceeds the specified value, ODP only returns an error packet but does not close connections, and the client does not close connections either, causing connection leaks.
• Fixed the issue where, when ODP V4.x is used for OceanBase Database V3.x, ODP cannot connect to the new primary cluster after a cluster failover.

V4.2.1 BP2 hotfix1

Version information

• Release date: October 17, 2023

• Version: V4.2.1 BP2 hotfix1

• RPM version: obproxy-4.2.1.0-20231017181929

Bug fixes

• Fixed the issue where ODP exits due to a PS memory leak.

• Fixed the issue where the connection to the Binlog service fails occasionally after the high availability feature is enabled for ODP.

• Modified the disaster recovery check criteria for the Binlog service.

• Fixed the issue where an exception occurs during the update of the configuration table when global settings are configured by specifying the cluster_name parameter.

• Fixed the issue where the value of the is_partition_hit parameter in the diagnostic log is true (which is expected to be false) due to inaccurate SQL routing.

V4.2.1 BP2

Version information

• Release date: September 05, 2023

• Version: V4.2.1 BP2

• RPM version: obproxy-4.2.1.0-20230905194130

Overview

Binlog service address change is supported.

Bug fixes

• Fixed the issue where, after enable_ldg is enabled in an Arm environment, a core dump is generated for ODP while simulating a network failure on a node by using iptables.

• Fixed the issue where disconnection occurs during running.

• Fixed the issue where disconnection occurs due to expired cluster information in a binlog request scenario.

• Fixed the issue where ODP falls into an infinite loop after login fails in some scenarios.

• Fixed the issue of memory bloat in routing diagnostics.

V4.2.1 BP1

Version information

• Release date: August 11, 2023

• Version: V4.2.1 BP1

• RPM version: obproxy-4.2.1.0-20230811111811

Bug fixes

• Fixed the issue where the show columns from db_name.table_name statement cannot be correctly recognized.

• Fixed the issue where parameters cannot be persisted in the routing diagnostics feature.

• Fixed the issue of memory leaks in the routing diagnostics feature.

• Fixed the issue where the process exits during a hot upgrade.

• Fixed the issue where the process exits because the memory of ODP is used up due to a memory leak in the connection diagnostics feature.

V4.2.1

Version information

• Release date: July 12, 2023

• Version: V4.2.1

• RPM version: obproxy-4.2.1.0-20230712162726

Overview

ODP V4.2.1 is a Long-term Supported (LTS) version of V4.2.x.

Feature updates

• Automatic session synchronization verification is supported.

• Access to a cluster by using its alias is supported.

• The GB18030 2022 character set is supported.

• The Show Trace feature is supported. For more information, see Show Trace.

• Forwarding of binlog-related statements is supported.

• The routing diagnostics feature is supported. For more information, see Overview.

• The connection diagnostics feature is supported.

• The forcible encryption attribute is supported for SSL.

• The general connection initialization mechanism is supported.

• A latency threshold is supported for weak-consistency reads. For more information, see Follower latency threshold.

Bug fixes

• Fixed the issue of ODP disconnection.

• Fixed the issue where an error is expected but the operation succeeds when a tenant-level parameter is deleted.

• Fixed the issue where you cannot configure multiple values when you update a parameter.

• Fixed the issue where the allowlist contains invalid CIDR blocks.

• Fixed the issue where the operation of inserting data into a table is hung when the utf16 character set is used.

• Fixed the issue where the error "received malformed packet" is returned when the root@proxysys account is used to log in to ODP after ODP is restarted.

• Fixed the issue where disconnection occurs when an IP address specified in the comment is enclosed with double quotation marks (").

• Fixed the issue where, when a three-segment connection string, in which the primary address of the cluster hosting the standby tenant is specified as the database IP address and the name of the cluster hosting the primary tenant is appended to the tenant name in the login username, is used for database connection, the primary tenant is connected but the error Cannot execute statement in a READ ONLY transaction is returned, indicating that data write is not supported.

• Fixed the issue where the parsing module of ODP may cause memory leaks.

• Fixed the issue where the performance deteriorates after some system variables are modified.

• Fixed the issue where distributed transaction routing must be used for the select CONNECTION_ID() statement.

• Fixed the issue of PL disconnection during calls.

• Fixed the issue where the connection to ODP is disconnected if the OK packet contains the last_insert_id field.

• Fixed the issue where ODP must support the attribute value 0 when reading connection attributes.