[Bug] [dinky-metadata-base] Fix the problem of permanent failure of metadata data source after MySQL wait_timeout closes idle connections (#4570) - #4571
Open
coderworld321 wants to merge 2 commits into
Conversation
github-actions
Bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AbstractJdbcDriver#connect():复用 ThreadLocal 缓存连接前,先通过 validationQuery 校验有效性;失效时先关闭旧连接再重建,并输出 warn 日志便于排查
AbstractJdbcDriver#isHealth():用真实查询探测代替 isClosed(), 避免"物理连接已被服务端关闭但客户端误判健康"
设置 breakAfterAcquireFailure=false,使 Druid 连接池在获取失败后可自恢复 (原 true 会导致数据源一次失败即永久瘫痪)
开启 keepAlive 并设置空闲回收时间(min/maxEvictableIdleTimeMillis), 保护池内空闲连接不被服务端踢除