Release 3.21.10.1

Release Notes:

We have released a bug-fixed version 3.21.10.1.

Bug-fixes:

• Upgrade log4j to 2.17.1
• Respective-sharding‘s view issues
• Can turn off the heartbeat recording
• Some possible hang scenarios
• Read-write separation hint statement failure problem
• Prepared statement bugs
• Back-end traffic control in read-write separation mode
• Support for com_field_list protocol in read-write separation mode
• In the scenario of read-write separation, add and delete slaves smoothly
• Error in load data with empty text
• Error with single node table ddl
• Memory leak caused by front-end slb

发行说明：

我们发布了3.21.10.1,这是个基于3.21.10.0的bug修复版本

问题修复:

• 升级log4j到 2.17.1
• 垂直拆分的view问题
• 可关闭心跳记录
• 一些可能hang的场景
• 读写分离hint语句失效问题
• prepared statement 的bug
• 读写分离模式下对后端流量的控制
• 读写分离模式下对com_field_list协议的支持
• 读写分离场景下，平滑增删从机
• 空文本的load data的错误
• 单节点表ddl的错误
• 前端slb引发的内存泄露

Release 3.21.06.3

Release Notes:

We have released a bug-fixed version 3.21.06.3.

Bug-fixes:

• Upgrade log4j to 2.17.1
• Respective-sharding‘s view issues
• Can turn off the heartbeat recording
• Some possible hang scenarios
• Read-write separation hint statement failure problem
• Prepared statement bugs
• Back-end traffic control in read-write separation mode
• Support for com_field_list protocol in read-write separation mode
• In the scenario of read-write separation, add and delete slaves smoothly
• Error in load data with empty text
• Error with single node table ddl
• Memory leak caused by front-end slb

发行说明：

我们发布了3.21.06.3,这是个基于3.21.06.2的bug修复版本

问题修复:

• 升级log4j到 2.17.1
• 垂直拆分的view问题
• 可关闭心跳记录
• 一些可能hang的场景
• 读写分离hint语句失效问题
• prepared statement 的bug
• 读写分离模式下对后端流量的控制
• 读写分离模式下对com_field_list协议的支持
• 读写分离场景下，平滑增删从机
• 空文本的load data的错误
• 单节点表ddl的错误
• 前端slb引发的内存泄露

Release 3.21.02.7

Release Notes:

We have released a bug-fixed version 3.21.02.7.

Bug-fixes:

• Upgrade log4j to 2.17.1
• Respective-sharding‘s view issues
• Can turn off the heartbeat recording
• Some possible hang scenarios
• Read-write separation hint statement failure problem
• Prepared statement bugs
• Back-end traffic control in read-write separation mode
• Support for com_field_list protocol in read-write separation mode
• In the scenario of read-write separation, add and delete slaves smoothly
• Error in load data with empty text
• Error with single node table ddl
• Memory leak caused by front-end slb

发行说明：

我们发布了3.21.02.7,这是个基于3.21.02.4的bug修复版本

问题修复:

• 升级log4j到 2.17.1
• 垂直拆分的view问题
• 可关闭心跳记录
• 一些可能hang的场景
• 读写分离hint语句失效问题
• prepared statement 的bug
• 读写分离模式下对后端流量的控制
• 读写分离模式下对com_field_list协议的支持
• 读写分离场景下，平滑增删从机
• 空文本的load data的错误
• 单节点表ddl的错误
• 前端slb引发的内存泄露

Release 3.20.10.8

Release Notes:

We have released a bug-fixed version 3.20.10.8.

Bug-fixes:

• Upgrade log4j to 2.17.1
• Respective-sharding‘s view issues
• Can turn off the heartbeat recording
• Some possible hang scenarios
• Read-write separation hint statement failure problem
• Memory leak caused by front-end slb

发行说明：

我们发布了3.20.10.8,这是个基于3.20.10.7的bug修复版本

问题修复:

• 升级log4j到 2.17.1
• 垂直拆分的view问题
• 可关闭心跳记录
• 一些可能hang的场景
• 读写分离hint语句失效问题
• 前端slb引发的内存泄露

Release 3.20.07.8

Release Notes:

We have released a bug-fixed version 3.20.07.8.

Bug-fixes:

• Upgrade log4j to 2.17.1
• Respective-sharding‘s view issues
• Can turn off the heartbeat recording
• Some possible hang scenarios
• Memory leak caused by front-end slb

发行说明：

我们发布了3.20.07.8,这是个基于3.20.07.7的bug修复版本

问题修复:

• 升级log4j到 2.17.1
• 垂直拆分的view问题
• 可关闭心跳记录
• 一些可能hang的场景
• 前端slb引发的内存泄露

Release 3.21.10.0

Release Notes:

We have released a new version 3.21.06.0.
Firstly, we must thank to the following people for their contributions to our community：@13611582598, @mwhei , @lenovore, @jmbkeyes .

Features:

• [#2866] Supports detach/attach cluster. More Detail,see doc.
• [#2844] Supports default sharding schema[alpha version]. More Detail,see doc.
• [#2845] New flow control: add backend read water level. More Detail,see doc.

Bug-fixes:

• [#11] EPollArrayWrapper.epollWait may cause 100% CPU .
• [#2896] show @@dbInstance command, READ_LOAD and WRITE_LOAD are always displayed as 0.
• [#2747] fakeMySQLVersion does not support MariaDB 10.x, thanks to @lenovore for reporting the bug.
• [#2750] support add/truncate/dop partition , thanks to @13611582598 for reporting the bug.
• [#2611] The problem of optimizing er table, thanks to @jmbkeyes for reporting the bug.
• [#2828] Three tables join, the result may be wrong, thanks to @mwhei for reporting the bug.
• Sometimes complex queries may cause memory leaks.

Breaking backward compatibility:

none

---

发行说明：

我们发布了新版本 3.21.10.0。
首先，我们必须感谢以下人士对我们社区的贡献：@13611582598, @mwhei , @lenovore, @jmbkeyes.

特性：

• [#2866] 支持单个dble脱离/回归集群. 更多详细信息，请参见 doc.
• [#2844] 支持默认的分片模式 [alpha功能]。更多详细信息，请参见doc.
• [#2845] 新的流量控制：添加后端读取水位。更多详细信息，请参见doc.

缺陷修复:

• [#11] EPollArrayWrapper.epollWait 可能导致 100% CPU。
• [#2896] show @@dbInstance 命令，READ_LOAD 和 WRITE_LOAD 始终显示为 0.
• [#2747] fakeMySQLVersion 不支持 MariaDB 10.x，感谢@lenovore 报告此问题。
• [#2750] 支持add/truncate/dop partition , 感谢@13611582598 报告此问题。
• [#2611] 优化er表问题，感谢@jmbkeyes 报告错误。
• [#2828] 三表join，结果可能有误，感谢@mwhei 报告bug。
• 有时复杂的查询可能会导致内存泄漏。

和旧版本的不兼容项：

无

Release 3.21.06.2

Release Notes:

We have released a bug-fixed version 3.21.06.2.

Bug-fixes:

• Execute dbGroup @@disable name ='dbGroup1';，sometimes hang.
• When create connection failed，totalConnection will be wrong and lead to the connection leak.
• When status of instance of mysql changed from disable to active，dble may still hang
• Sometimes complex query may cause memory leak.
• [#2873]The problem of set autocommit=true
• The problem of manager command show @@connection.sql
• When cluster mode, execute ddl may hang
• show @@dbInstance command, READ_LOAD and WRITE_LOAD are always displayed as 0.

发行说明：

我们发布了3.21.06.2,这是个基于3.21.06.0的bug修复版本

问题修复:

• 执行dbGroup @@disable name ='dbGroup1';偶现hang住
• 连接创建失败时，连接数统计的问题导致的连接泄漏
• mysql实例从disable到active状态后，dble 不可用
• 有时复杂的查询可能会导致内存泄漏。
• [#2873]set autocommit=true 的问题
• 管理端口执行show @@connection.sql报错
• 集群环境下dble执行ddl语句hang住
• show @@dbInstance 命令，READ_LOAD 和 WRITE_LOAD 始终显示为 0.

Release 3.21.02.4

Release Notes:

We have released a bug-fixed version 3.21.02.4.

Bug-fixes:

• Execute dbGroup @@disable name ='dbGroup1';，sometimes hang.
• When create connection failed，totalConnection will be wrong and lead to the connection leak.
• When status of instance of mysql changed from disable to active，dble may still hang
• Sometimes complex query may cause memory leak.
• [#2873]The problem of set autocommit=true
• The problem of manager command show @@connection.sql
• When cluster mode, execute ddl may hang
• show @@dbInstance command, READ_LOAD and WRITE_LOAD are always displayed as 0.

发行说明：

我们发布了3.21.02.4,这是个基于3.21.02.2的bug修复版本

问题修复:

• 执行dbGroup @@disable name ='dbGroup1';偶现hang住
• 连接创建失败时，连接数统计的问题导致的连接泄漏
• mysql实例从disable到active状态后，dble 不可用
• 有时复杂的查询可能会导致内存泄漏。
• [#2873]set autocommit=true 的问题
• 管理端口执行show @@connection.sql报错
• 集群环境下dble执行ddl语句hang住
• show @@dbInstance 命令，READ_LOAD 和 WRITE_LOAD 始终显示为 0.

Release 3.20.10.7

Release Notes:

We have released a bug-fixed version 3.20.10.7.

Bug-fixes:

• Execute dbGroup @@disable name ='dbGroup1';，sometimes hang.
• When create connection failed，totalConnection will be wrong and lead to the connection leak.
• When status of instance of mysql changed from disable to active，dble may still hang
• Sometimes complex query may cause memory leak.
• [#2873]The problem of set autocommit=true
• The problem of manager command show @@connection.sql

发行说明：

我们发布了3.20.10.7,这是个基于3.20.10.5的bug修复版本

问题修复:

• 执行dbGroup @@disable name ='dbGroup1';偶现hang住
• 连接创建失败时，连接数统计的问题导致的连接泄漏
• mysql实例从disable到active状态后，dble 不可用
• 有时复杂的查询可能会导致内存泄漏。
• [#2873]set autocommit=true 的问题
• 9066端口执行show @@connection.sql报错

Release 3.20.07.7

Release Notes:

We have released a bug-fixed version 3.20.07.7.

Bug-fixes:

• Execute dbGroup @@disable name ='dbGroup1';，sometimes hang.
• When create connection failed，totalConnection will be wrong and lead to the connection leak.
• When status of instance of mysql changed from disable to active，dble may still hang
• Sometimes complex query may cause memory leak.

发行说明：

我们发布了3.20.07.7,这是个基于3.20.07.5的bug修复版本

问题修复:

• 执行dbGroup @@disable name ='dbGroup1';偶现hang住
• 连接创建失败时，连接数统计的问题导致的连接泄漏
• mysql实例从disable到active状态后，dble 不可用
• 有时复杂的查询可能会导致内存泄漏。