John Niang

Results 545 comments of John Niang
trafficstars

暂时先不修改 Halo 的配置,建议通过 https://help.aliyun.com/zh/rds/apsaradb-rds-for-mysql/view-the-parameters-of-an-apsaradb-rds-for-mysql-instance 检查一下 MySQL 服务器运行配置。

Hi @Oniokey , 我刚刚发现当前 Issue 此前已经有人提到过,请参考:。看看能否解决你的问题呢? /triage duplicate

Hi @Oniokey , I found there is [a similar issue](https://github.com/r2dbc/r2dbc-pool/issues/209) from upstream. We have to wait it to be resolved. 我发现上游有一个类似的 Issue,我们可以关注一下。

/retitle Suddenly encountered a "Connection validation failed" error

Hi @Oniokey ,方便提供发生错误时的完整日志文件吗,我需要之前之前具体发生了什么。不出意外的话,可能会有以下警告日志: ```java 2024-10-17T00:15:46.296+08:00 WARN 52493 --- [ctor-tcp-nio-10] i.a.r.mysql.client.ReactorNettyClient : Connection unexpectedly closed ```

Hi @Oniokey ,感谢反馈! 出现这个警告就说明数据库连接池中的部分连接已经断开了。目前尚不清楚为什么。RDS MySQL 的 wait_timeout 配置是 24 小时,interactive_timeout 配置是 8 小时,而 Halo 侧的连接池的 spring.r2dbc.pool.max-idle-time 配置是 30 分钟(如果你没有额外配置过),这样的配置应该是不会出现以上错误的,除非数据库重启了。 我在本地测试了两种场景都会出现以上警告: 1. 数据库重启(必现) 2. MySQL wait_timeout < spring.r2dbc.poo.max-idle-time(必现)

There is a similar issue about the error "Connection unexpectedly closed", please refer to .

> If I understand correctly, the issue is coming from upstream and they have already worked on fixing it, with subsequent halo merging into the upstream fix to get back...

Hi @Oniokey , please help us verify if this issue is resolved.