Releases: oceanbase/obproxy
Releases · oceanbase/obproxy
v3.2.3
RELEASE NOTE
| Item | Description |
|---|---|
| Release date | 2022-3-30 |
| Release number | V3.2.3 |
| Commit number | 7db4636 |
About this version
Feature:
- Support public cloud shared proxy connection number resource isolation
- Support public cloud shared proxy tenant level whitelist
- Support shared proxy cluster configuration push
- Support hot restart
- Supports partition routing for Timestmp data types
- Support client-side Execute optimization, allow without Param Type
- Proxyd.sh supports port modification, rslist startup, and configurl startup
- PS memory optimization
- 16C model performance optimization
- When accessing the cluster for the first time, after OBProxy obtains the RSList from the ConfigServer, the All Server List is obtained asynchronously and adjusted to obtain it synchronously
- Log compression can be turned on with enable_syslog_file_compress=True
- Full username strict mode can be enabled by enable_full_username=True
- You can increase the SQL length of obproxy_digest.log by setting the digest_sql_length parameter
- Added support for partition routing for timestamp type and negative numbers
- Added support for DDL statements in sharding scenarios
- Added tenant-level SSL link encryption
- Supports splicing URLs by zone
- OB Sharding supports Join
Bugfix:
- Fix the problem that the new password under the newly deployed cluster etc is inconsistent with the old password
- Fix ODP unable to handle configurations larger than 4K, currently there is no limit to configuration size
- Fix the cluster without LDG. After the enable_ldg switch is turned on, the proxy stops updating the location cache, resulting in no sense of offline machines.
- Fix Under the 2.0 protocol, the data returned to the driver by the ps and fetch protocols is incorrect, resulting in the client hang problem
- Fix mutli swichover obproxy core at databuff_print_key_obj<oceanbase::common::ObLogPrintPointerCntx
- Fix obproxy memory leak caused by frequent push of current limiting rules
- Fix inaccurate routing in col = ("123") mode
- Fix too many current-limiting rules causing the push to fail to take effect
- Fix obproxy memory leak caused by frequent push of current limiting rules
- Fix After repairing the failover of the standby database into the main database, after the original main database is down, the proxy will have a short time to route the request to the original main database
- Fix Failed to establish connection without specifying cluster id within 3 minutes after lossless FO
- Fix After repairing the deletion of the standby database, continue to send requests to the old clusterId
- Fix the problem that the new protocol link proxy cursor scene, when the fench reaches the second value, it will be rammed
- Fix the problem of ps cursor ramming under non-compression protocol
- Fix a new connection reporting too many connections error
- Fix the case-insensitive name field of the ssl_config configuration table, resulting in unreasonable configuration reading logic
- Fix Compression and 2.0 protocol, obdump import data will be hung
- Fix the new protocol, refcursor cannot get the value when there are other out parameters
- Fix obproxy core at oceanbase::common::ObObjCmpFuncs::compare null safe
- Fix obproxy core at oceanbase::common::ObTimeConverter::str_to_digit_with_date
- Fix the error -5560, Unknown prepared statement handle when bmsql opens ps when the compression protocol is enabled