Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the scaling thread(connection-pool-evictor-thread) exited unexpectedly #3746

Closed
wenyh1 opened this issue Jun 16, 2023 · 0 comments · Fixed by #3698
Closed

the scaling thread(connection-pool-evictor-thread) exited unexpectedly #3746

wenyh1 opened this issue Jun 16, 2023 · 0 comments · Fixed by #3698
Assignees
Labels
Milestone

Comments

@wenyh1
Copy link
Member

wenyh1 commented Jun 16, 2023

dble版本:3.20.10.14

0、初始配置
db.xml中的minCon=4
sharding.xml中有sharding_2_t1表,shardingNode="dn1,dn2", dn1,dn2均对应的ha_group1;
dble启动;此时语句后端连接池中会有4条连接
1、调整配置db.xml中以下三个参数,minCon不变;在9066中执行 reload @@config_all;:
8718a7bc-cf43-493f-aa5e-cc6825cc2425
扩缩容周期为:timeBetweenEvictionRunsMillis=10000ms ,意味着没间隔10s进行一次扩缩容

3、在3个8066连接中分别:

begin;
select * from sharding_2_t1;

最后3个一起执行 commit
4、在此时9066中执行select * from backend_connections where used_for_heartbeat='false' and state='idle', 预计能查出6条连接;

5、在进入一次扩缩容周期中,预计会回收2条连接,且有2条扩缩容日志打印'[connection-pool-evictor-thread]......省略....before cleanup db instance[M1]';待这次扩缩容周期结束后,预计查出 4条连接;

实际,第5步后,在管理端依旧能查出6条数据,且没有扩缩容的日志打印;此外发现后续的日志中,扩缩容线程connection-pool-evictor-thread 没有再出现过;通过jstack 观察也没有 connection-pool-evictor-thread这个线程。
看起来 connection-pool-evictor-thread 被意外的关闭了

(association inner-2227)

@wenyh1 wenyh1 changed the title 扩缩容线程意外退出 The scaling thread(connection-pool-evictor-thread) exited unexpectedly Jun 16, 2023
@wenyh1 wenyh1 self-assigned this Jun 16, 2023
@wenyh1 wenyh1 added this to the 3.23.04.0 milestone Jun 16, 2023
@wenyh1 wenyh1 added the bug label Jun 16, 2023
@wenyh1 wenyh1 changed the title The scaling thread(connection-pool-evictor-thread) exited unexpectedly the scaling thread(connection-pool-evictor-thread) exited unexpectedly Jun 16, 2023
@wenyh1 wenyh1 closed this as completed Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant